chore(release): prepare v0.5.0 - #62
Merged
Merged
Conversation
Bumps all nine workspace packages and every internal @changesafe/* range from 0.4.1 to 0.5.0. The currently-published 0.4.1 core carries a real skip-legitimacy gap (PR #61) and a broken Kubernetes eval path (PR #60); this is not a routine version bump but the release that gets those fixes into published hands. No breaking changes: policyCoverage is an additive optional receipt field, Terraform's new PLAN_CONTEXT_REQUIRED policy replaces a skip that already existed, and Kubernetes eval support only adds a domain --domain kubernetes could not previously use. CORE_POLICY_VERSION and TERRAFORM_POLICY_VERSION move independently of the package semver, as always. This prepares the release; it does not publish. Publishing still requires an explicit owner-authorized tag and GitHub Release. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a5a8872b0c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
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".
… published Fixes review feedback on the v0.5.0 prep PR: the example GitHub Action workflow, README, and docs/LAUNCH.md all pointed wonkwonlee/ChangeSafe@v0.5.0 before that tag exists, so a workflow copied from the example would fail to resolve the action rather than run the gate. Reverted those to v0.4.1 (still published and valid) and reworded "canonical" claims to say v0.5.0 is prepared but not yet published, matching what MEMORY.md's release-status section already said correctly. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
5 tasks
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
The currently-published
@changesafe/core@0.4.1on npm carries the universal-policy skip-legitimacy gap PR #61 fixed, and the CLI'schangesafe eval --domain kubernetes(PR #60) was unusable until that PR merged. Both are real fixes to already-published behavior, not just accumulated features — this prepares the release that gets them into published hands.package.json+ every internal@changesafe/*dependency range) from0.4.1→0.5.0.CORE_POLICY_VERSION→core-v0.2.0,TERRAFORM_POLICY_VERSION→terraform-v0.2.0(already landed in PR fix(core): enforce universal-policy skip legitimacy, record it on receipts #61; a v0.5.0 receipt is not directly comparable to a v0.4.x one).docs/RELEASE_NOTES_v0.5.0.md, updatesdocs/LAUNCH.md's release-truth log,README.md's package/Action-version references,MEMORY.md's release-status section, and the example GitHub Action workflow's pinned tag.policyCoverageis an additive optional receipt field,PLAN_CONTEXT_REQUIREDreplaces a skip that already existed, Kubernetes eval support only adds a previously-broken domain.This prepares the release; it does not publish. Publishing needs an explicit owner-authorized git tag and GitHub Release, per the repo's publish workflow (
releaseevent trigger).Test plan
npm installnpm run lintnpm run typechecknpm run build:clinpm test— 1187 passed, 4 skippednpm run buildnode packages/cli/dist/changesafe.js scenario checknode packages/cli/dist/changesafe.js scenario gallery --checknode packages/cli/dist/changesafe.js --version→changesafe 0.5.0🤖 Generated with Claude Code