Repository navigation
chore: refresh P1 release assessment for 0.4.3 - #213
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
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.
Refresh the Phase 1 supply-chain assessment to 2026-09-07 after rechecking the candidate. The existing 2026-08-23 assessment fails the same-day gate for
v0.4.3publication.This changes only the assessment timestamp. The five candidate package digests and Experimental/Stable lifecycle states remain unchanged. Part of #210; publication and external verification remain outstanding.
Validation:
npm run test:p1-supply-chain: 68 passed.npm test: 849 passed, 0 failed, 3 existing TODOs; includes exact packed-artifact journeys.npm run validate:release -- --tag v0.4.3: passed.npm run validate:p1 -- --require-publish-ready,npm run validate:p0, andnpm run validate:acceptance: passed.node scripts/verify-experimental-release.mjs --phase candidate --json: all five digests match.All five npm package write permissions and Trusted Publisher configurations were verified. The separate preflight fan-out was declined by the maintainer. The maintainer approved the one-line existing-file footprint exception.