chore(release): prepare 0.233.0 - #1261
Conversation
v0.232.0 was tagged at 602e4fb (#1257 + #1260) four minutes before #1259 merged, so #1247's runtime half — the released terminal record, retainedExecution, fleetYield — is not in 0.232.0. main declared 0.232.0 with it inside. This moves those CHANGELOG paragraphs under 0.233.0, leaves 0.232.0 saying exactly what shipped, and regenerates the three artifacts that embed the version. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Consumer integration owner readback: I preserved #1259 and #1261 and am updating the Sandbox 0.41 compatibility patch to Runtime 0.233.1 (Bench 0.13.3). The 0.233.0 tag/publisher remains with this release owner; I will not modify it. Scope remains the compatible SDK peer/catalog bounds and generated release metadata. Please reserve 0.233.1 for that dependency patch, needed by App/Traces/ADC. All 4,083 tests passed on the earlier source; 182 directly affected tests, types, and docs generation passed after integrating #1259. Package/edge checks passed before that integration; the final integrated package check is still required. |
v0.232.0was tagged at602e4fbd(#1257 + #1260) at 06:17:44Z, four minutes before #1259 merged at 06:21:32Z. So 0.232.0 ships #1244/#1248 but not #1247's runtime half (released terminal record,retainedExecution,fleetYield), whilemaincurrently declares 0.232.0 with #1259 inside it.This is the version cut for what
mainnow carries beyond the tag:release:prepare 0.233.0(package.json,docs/canonical-api.md, testing fixtures,docs/api), and the CHANGELOG's #1247 paragraphs moved under a new## 0.233.0so## 0.232.0says exactly what shipped. No source change.check:version-bumppays #1259's export changes with 0.232.0 → 0.233.0.Tag
v0.233.0after this merges and after the 0.232.0 Publish run (35063076617) finishes, so the two never race the same workflow.🤖 Generated with Claude Code