Anton Vinogradov created IGNITE-28821:
-----------------------------------------
Summary: Protected Classes CI check: report as warning instead of
failing the PR build
Key: IGNITE-28821
URL: https://issues.apache.org/jira/browse/IGNITE-28821
Project: Ignite
Issue Type: Task
Reporter: Anton Vinogradov
Assignee: Anton Vinogradov
The "Protected Classes" GitHub Actions workflow
(.github/workflows/check-protected-classes.yml) currently fails the PR build
(exit 1) whenever a change touches @Order-annotated (protected) classes, which
may break rolling-upgrade compatibility.
This hard failure red-flags PRs even for intentional, compatible changes and
creates friction; the workflow was disabled manually on 2026-05-27 for this
reason.
Proposal: instead of failing the build, publish a separate, non-blocking check
"Rolling upgrade compatibility" with the action_required conclusion (yellow
marker), keeping the existing explanatory PR comment and the `compatibility`
label. The main "Rolling Upgrade check" job then always succeeds, and the
rolling-upgrade risk is surfaced for reviewer attention without blocking the
merge.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)