Repository navigation
ci: report the manifest without failing on it - #7
Merged
Merged
Conversation
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.
Every pinned rebuild for a new release ended red: the manifest carries the tag (and here new fields), so it always differs from the release it rebuilds, and red stopped meaning anything.
compare-sysrootnow reports the manifest by the keys that changed and leaves it out of the fatal set; any other differing file still fails the job.Checked locally against the 2026.11.03 artifact vs 2026.10.13: exit 0,
manifest … differs in: buildRoot hostTypelibs licensedProjects ndkRoot sources tag typelibs. With one byte appended to libadwaita-1.so:differing content: 1, exit 1.