[PR] IGNITE-28821 Protected Classes CI check: report as warning instead of failing the PR build [ignite]

["anton-vinogradov (via GitHub)" <gi...@apache.org>]

anton-vinogradov opened a new pull request, #13279:
URL: https://github.com/apache/ignite/pull/13279

   ## What
   The `Protected Classes` workflow no longer fails the PR build when a change touches `@Order`-annotated (protected) classes. Instead it publishes a separate, non-blocking check `Rolling upgrade compatibility` with the `action_required` conclusion (yellow marker), keeping the existing PR comment and `compatibility` label.
   
   ## Why
   A hard failure (`exit 1`) red-flagged PRs even for intentional, compatible changes, creating friction (the check was disabled manually on 2026-05-27 for this reason). A warning surfaces the rolling-upgrade risk for reviewer attention without failing the build.
   
   ## Notes
   - The `Rolling Upgrade check` job now always succeeds.
   - The new check is non-blocking unless added to required status checks.
   - `checks: write` permission added for the Checks API call.
   
   Jira: https://issues.apache.org/jira/browse/IGNITE-28821
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@ignite.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org