fix: publish SHA-256 node-agent package manifests - #7
Merged
Conversation
Publish SHA-256 manifests inside the Linux compatibility archive while retaining legacy SHA-1 manifests, and verify both chains in release CI.
Bind the existing header-only justification to the exact linux-libc-dev package and Critical/High identifiers observed in the current pinned Dapper build.
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
1 participant
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.
Result
Current hosts reject the Linux compatibility archive because it contains only legacy SHA-1 manifests. This change preserves those manifests, adds SHA-256 manifests, and verifies both chains after extraction in the release workflows.
Focused verification