docs: record the verified v0.5.0 provenance - #63
Merged
Conversation
v0.5.0 is live: all five packages published at 0.5.0, attestations verified (gitHead c1ae07e matches refs/tags/v0.5.0), npm audit signatures reports verified registry signatures and attestations for the installed tree. The registry-installed CLI was exercised end to end: gating a destructive Terraform plan exits 1 with PLAN_CONTEXT_REQUIRED visible in the findings, and @changesafe/domain-kubernetes imports directly under Node ESM. Bumps the GitHub Action example and README/LAUNCH pinned references from v0.4.1 to v0.5.0 now that the tag actually resolves, and records v0.4.1 as superseded rather than canonical. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
v0.5.0 is published (triggered by the GitHub Release created after #62 merged). This records what was actually verified, mirroring the v0.4.1 provenance-recording pattern (#59):
0.5.0;dist.attestationsonchangesafe@0.5.0and@changesafe/core@0.5.0both resolve, andgitHeadmatchesc1ae07e— the exact commitrefs/tags/v0.5.0points at.npm audit signaturesagainst a throwaway install: verified registry signatures and verified attestations for the whole tree.changesafe --version→0.5.0; gating a destructive Terraform plan → exit 1,blocked: true,PLAN_CONTEXT_REQUIREDvisible in the findings (the exact policy this release added);@changesafe/domain-kubernetesimports directly under Node ESM.examples/github-actions/gate-terraform-plan.yml) and the pinned references inREADME.md/docs/LAUNCH.mdfrom@v0.4.1to@v0.5.0now that the tag actually resolves — a review comment on chore(release): prepare v0.5.0 #62 correctly caught that bumping these before publish would have broken any workflow copied from the example in the meantime.docs/LAUNCH.mdandMEMORY.mdnow record v0.4.1 as superseded rather than canonical.Nothing in
verification/was touched — that directory is the frozen v0.1.0 snapshot and stays that way regardless of newer releases.Test plan
npm run lintnpm run typechecknpm test— 1187 passed, 4 skipped@v0.4.1references remain in README/LAUNCH/the example workflow🤖 Generated with Claude Code