Repository navigation
chore(release): prepare 0.8.3 - #245
Conversation
|
🦞👀 Pull request received. I will update this pull request when review starts. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![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: 34aed9d2dd
ℹ️ 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".
| { | ||
| "name": "clawpatch", | ||
| "version": "0.8.2", | ||
| "version": "0.8.3", |
There was a problem hiding this comment.
After bumping the package to 0.8.3, the manual release check in docs/release-prep.md:43-47 still dispatches with tag_name=v0.8.2. In that documented scenario, --ref main checks out this 0.8.3 package while .github/workflows/release.yml:58-61 rejects the supplied 0.8.2 release version, so the prescribed dry run now always fails before validation. Update the example to v0.8.3 or derive the tag dynamically.
Useful? React with 👍 / 👎.
Prepare clawpatch 0.8.3 as a patch release for the existing provider JSON recovery fix, a development-tooling security fix, and dependency updates.
Preserve every Unreleased bullet and contributor credit, put the user-visible fix first with a one-line Highlights summary, and open the empty 0.8.4 Unreleased section. This PR only changes package version and changelog metadata; publication follows the existing GitHub Actions release workflow after exact-head CI and a successful dry run.
Validation: full Linux gate passed (970 tests passed, 2 skipped), including typecheck, lint, formatting, build, packaged CLI smoke, dry-run package contents, and a clean dependency audit. Independent Codex autoreview found no actionable P0–P2 findings. A multiset comparison verifies that all eight changelog bullets remain intact.