fix: safely backfill legacy signed npm releases - #166
Merged
mldangelo-oai merged 1 commit intoJul 31, 2026
Merged
Conversation
Collaborator
Author
|
@codex review |
|
Codex Review: Didn't find any major issues. Already looking forward to the next diff. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
|
Security review completed. No security issues were found in this pull request. Reviewed commit: Only the user who started this review can view the report in Codex. ℹ️ About Codex security reviews in GitHubThis is an experimental Codex feature. Security reviews are triggered when:
Once complete, Codex will leave suggestions, or a comment if no findings are found. |
ianw-oai
approved these changes
Jul 31, 2026
mldangelo-oai
deleted the
mdangelo/codex/backfill-legacy-release-provenance-20260730
branch
July 31, 2026 00:32
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
2 participants
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.
Backfills the two immutable historical npm releases whose public registry metadata predates gitHead publication. The GitHub-release workflow now verifies the exact SLSA attestation, protected publishing run, repository, release tag, source commit, and tarball bytes before accepting missing gitHead for 0.1.0 or 0.1.1 only. All later releases continue failing closed when gitHead is missing; mismatched metadata is always rejected. Validation: 176 release automation tests passing, TypeScript typecheck, Prettier, and successful live verification of the real protected 0.1.0 and 0.1.1 release artifacts and npm provenance.