Repository navigation
Conversation
This branch has not been deployed
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.
Harden the release pipeline by pinning every action and build tool, verifying the Binaryen archive checksum, and removing mutable
latestdownloads.Release artifacts now build in jobs with read-only repository permissions. The publishing job consumes those artifacts from the exact workflow commit, validates checked-in versions and lockfiles, and publishes with
--lockedrather than regenerating dependency resolutions during release.Version and changelog updates must now be reviewed and committed before dispatching the release workflow.
This fixes SEC-05 from #38. Tag immutability and release attestations remain isolated to SEC-20.