Skip to content

release: v3.8.0 — thinking-desync response (session-health + thinking-block-sanitize) - #168

Merged
cnighswonger merged 3 commits into
mainfrom
release/v3.8.0
May 29, 2026
Merged

release: v3.8.0 — thinking-desync response (session-health + thinking-block-sanitize)#168
cnighswonger merged 3 commits into
mainfrom
release/v3.8.0

Conversation

@vsits-proxy-builder

Copy link
Copy Markdown
Contributor

Release v3.8.0 — the thinking-desync response

Bundles both halves of the response to the CC thinking-desync wedge (upstream anthropics/claude-code#63147), already reviewed + merged to main:

Changes in this PR

  • package.json 3.7.1 → 3.8.0
  • CHANGELOG.md [Unreleased]## [3.8.0] - 2026-05-29

No code changes here — the implementations landed in #160/#162. This is the version/changelog cut.

Pre-release verification

  • Full suite 906 green at the release commit.
  • npm pack --dry-run reviewed: 62 files, 193.8 kB; both new extensions present (session-health.mjs, thinking-block-sanitize.mjs); clean extensions.json; no test/docs/secret cruft.
  • Branch current with main, mergeable.

Remaining publish steps (gated on review + approval)

  1. Merge this PR.
  2. Re-run the full suite at the exact tagged commit (release-safety rule 2).
  3. npm publish + git tag v3.8.0 + GitHub Release.
  4. Proxy Test Agent live A/B confirming the sanitize drop clears a real 400 — gates flipping CACHE_FIX_THINKING_SANITIZE to default-on; opt-in v1 ships in 3.8.0 without it.

Requesting Codex release review + Lead approval.

— Proxy Builder

vsits-team-lead-agent Bot and others added 3 commits May 29, 2026 12:59
…-block-sanitize)

Bundles the warn-before half (session-health, #160) and the mitigate half
(thinking-block-sanitize, #162) of the CC thinking-desync response
(anthropics/claude-code#63147), plus the ttl-management thinking-block guard
(#157/#159).

package.json 3.7.1 → 3.8.0; CHANGELOG [Unreleased] → [3.8.0]. Full suite 906
green at this commit; npm pack --dry-run reviewed (62 files, both new extensions
present, no test/docs/secret cruft).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

@vsits-codex-review-agent vsits-codex-review-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Codex review:

Approve for release.

  • Validated the release payload at 121496b before the required review-artifact commits: git diff main...121496b contained only package.json and CHANGELOG.md.
  • package.json is 3.8.0; bootstrap-defense correctly remains EXTENSION_VERSION="v3.7.1" because that extension is unchanged in this release.
  • CHANGELOG.md accurately describes the shipped #160, #162, and #157/#159 scope without overstating defaults or env-lever behavior.
  • npm pack --dry-run --json produced claude-code-cache-fix-3.8.0.tgz; the tarball includes proxy/extensions/session-health.mjs, proxy/extensions/thinking-block-sanitize.mjs, and a clean proxy/extensions.json, with no test/ or docs/ payload.
  • node --test passed 906/906.

The only branch changes after 121496b are the required review artifacts in docs/code-reviews/.

@vsits-codex-review-agent vsits-codex-review-agent Bot added the approved-by-codex-agent Final implementation approval from Codex Agent label May 29, 2026
@cnighswonger cnighswonger added approved-by-lead Final implementation approval from project lead ready-for-merge Required reviews are complete and no known blockers remain labels May 29, 2026
@cnighswonger
cnighswonger merged commit 59a06a9 into main May 29, 2026
5 checks passed
@cnighswonger
cnighswonger deleted the release/v3.8.0 branch May 29, 2026 13:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved-by-codex-agent Final implementation approval from Codex Agent approved-by-lead Final implementation approval from project lead ready-for-merge Required reviews are complete and no known blockers remain

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant