feat: add opt-in cross-module compatibility warnings - #676
Open
AlexanderLanin wants to merge 1 commit into
Open
Conversation
Refs eclipse-score#674 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
AlexanderLanin
requested review from
MaximilianSoerenPollak,
dcalavrezo-qorix and
nradakovic
as code owners
July 31, 2026 13:49
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //src:license-checkStatus: Click to expand output |
|
The created documentation from the pull request is available at: docu-html |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Today, any validation mismatch in an integrated documentation build aborts the build. This is correct and safe, but it prevents integration entirely until every participating module is perfectly aligned.
This feature allows integration to proceed during temporary version skew, but only for explicitly enabled, well-defined cross-module compatibility cases. It does not suppress arbitrary validation failures: local findings and every non-enabled category remain fatal.
Enabled compatibility findings stay highly visible: they are emitted in the build output, shown prominently on the generated documentation start page, and written to JSON and HTML reports for CI follow-up.
Supported opt-in cases
Refs #674