Skip to content

chore(release): prepare 0.8.3 #245

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
steipete merged 1 commit into from
Oct 20, 2026
Merged

chore(release): prepare 0.8.3 #245

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,15 +1,18 @@
# Changelog

## 0.8.3 - Unreleased
## 0.8.4 - Unreleased

## 0.8.3 - 2026-10-20

**Highlights:** Provider JSON recovery handles unmatched braces in prose, and the coverage toolchain receives a Source Map JS security fix.

- Fixed provider JSON extraction to recover structured results after unmatched braces in leading prose, thanks @goutamadwant and @notlakshitha.
- Updated the coverage toolchain's Source Map JS dependency to 1.2.2 to fix an indexed source-map denial of service (GHSA-68fv-2mgg-jv7q).
- Updated Vite to 8.3.4, pnpm to 11.28.6, and the release workflow's npm CLI to 12.2.0 within the 48-hour dependency release-age policy.
- Updated Zod to 4.6.7, Vitest and V8 coverage to 5.0.5, Oxfmt to 0.73.0, Oxlint to 1.88.0, and CodeQL to 4.39.0 within the 48-hour dependency release-age policy, thanks @dependabot[bot].
- Added a no-publish release workflow dry run that validates the selected ref and defaults on for manual dispatch.
- Fixed provider JSON extraction to recover structured results after unmatched braces in leading prose, thanks @goutamadwant and @notlakshitha.
- Updated Node setup to 7.1.0, CodeQL to 4.38.3, and both the TruffleHog action and scanner to 3.99.2, thanks @dependabot[bot].
- Updated Oxfmt to 0.72.0 and Oxlint to 1.87.0 for repository formatting and linting, thanks @dependabot[bot].

- Updated Node 22 typings to 22.20.5, Vitest and V8 coverage to 5.0.3, Vite to 8.3.2, and pnpm to 11.28.4 within the 48-hour dependency release-age policy, thanks @dependabot[bot].

## 0.8.2 - 2026-10-01
Expand Down
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "clawpatch",
"version": "0.8.2",
"version": "0.8.3",

@chatgpt-codex-connector chatgpt-codex-connector Bot Oct 20, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Update the documented dry-run tag with the package version

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 👍 / 👎.

"description": "Automated code review that lands fixes.",
"license": "MIT",
"repository": {
Expand Down
Loading