chore(release): 0.2.0 - #1105
Merged
Merged
Conversation
Synchronized minor bump across the six publishable libraries, matching the convention in docs/RELEASE.md. The headline change is that an agent stream closing without terminal evidence is now reported as an interruption rather than a completed turn, and only the recovery the adapter can prove is safe gets offered. Consumer-visible: retryable on an interrupted AgentError is now true only when recovery is retry, so an interruption whose request may already have reached the server no longer offers a replay. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
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.
Synchronized minor bump across the six publishable libraries, from 0.1.0 to 0.2.0.
docs/RELEASE.mdsets minor bumps as the convention, and the last two releases both landed this way: as a pull request, with the tag placed on the merged commit afterwards.What is in this release
The headline change is pull request 1103. An agent stream that closes without terminal evidence is now reported as an interruption rather than a completed turn, and only the recovery the adapter can prove is safe gets offered: Retry when the request never left, a read-only status check where the backend supports one, otherwise a plain explanation and no action.
Consumer-visible behaviour change
retryableon aninterruptedAgentErroris now true only whenrecoveryisretry. Previously every interruption was retryable. An interruption whose request may already have reached the server no longer offers a replay, because replaying it could duplicate a tool call or a booking.Anyone whose UI branches on
retryablealone will find that interruptions stop rendering a Retry button. The new branch to add readsrecovery, andAgentgained an optionalcheckStatusfor the read-only check. The error handling guide covers both.How this was prepared
Versioned with
nx release version --specifier=minor, agent context files regenerated so they state v0.2.0, changelog generated bynx release changelog. Two deliberate deviations from a plain run, both to keep the tag honest:The generated
package-version.tsconstants were deliberately not included. The pre-version build embeds the previous version, whichdocs/RELEASE.mdwarns about, so committing them would have written a different stale value. They are regenerated correctly at publish time. Worth noting separately that the copies committed on main are stale at 0.0.66 against manifests at 0.1.0; that predates this release and is not fixed here.package-lock.jsonwas checked for the macOS regeneration hazard. All eight@next/swc-*entries survive across darwin, linux and win32.🤖 Generated with Claude Code