Hi Kirill, This check is related to the Rolling Upgrade initiative described in IEP-132. https://cwiki.apache.org/confluence/display/IGNITE/IEP-132+Rolling+Upgrade
The main idea is that Ignite should eventually support upgrading a cluster node by node, without full cluster downtime. To make that possible, some parts of the codebase must preserve compatibility between old and new nodes in a mixed-version topology, especially communication/discovery messages, management API DTOs, binary metadata/marshalling-related classes, and other version-sensitive protocol structures. The new Rolling Upgrade check is an early guardrail for that. It does not run a full rolling-upgrade scenario. Instead, it detects whether a PR touches Java classes that look compatibility-sensitive, currently classes using the org.apache.ignite.internal.Order annotation. If such files are changed, the check fails intentionally, adds the compatibility label, and posts a warning comment asking reviewers to check rolling-upgrade compatibility. So, if it fails, it does not necessarily mean that the PR is wrong. It means: “please pay extra attention; this change may affect wire/protocol compatibility.” Sincerely, Dmitriy Pavlov ср, 29 апр. 2026 г. в 14:59, ткаленко кирилл <[email protected]>: > I noticed there's a new `Rolling Upgrade check` test for PR, but I > couldn't find any information about it. > Does anyone know anything about it, what it means, and what to do if it > fails, like this one? > > https://github.com/apache/ignite/actions/runs/25103824857/job/73559768623?pr=13080 >
