chore: version packages#413
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@vicoop-bridge/client@0.35.5
Patch Changes
cd33e7a: Canonicalize
rate_limitedfailure messages so post-content OpenAI-compatibleclients auto-retry.
Once a stream has committed content, a downstream OpenAI-compatible client
(e.g. opencode) can no longer see the machine
code—@ai-sdk/openai-compatiblecollapses an in-band
{error:{...}}chunk to just its message string — so itsretry heuristic classifies on the message text alone. That heuristic keys on the
literal phrases "rate limit" / "too many requests", but
normalizeTaskFailErrorclassifies rate limits more broadly (a bare
429,rate-limitedwith a hyphen,or
rate_limitwith an underscore). A genuine rate limit whose upstream textlacked the exact phrase therefore would not trigger the client's auto-retry.
normalizeTaskFailErrornow prefixes such messages withrate limit:when thefinal code is
rate_limitedand the phrase is absent. This is an honesttranslation, not a failure-mode change — the branch is only reached for errors
already classified as rate limits — and the original upstream detail is preserved
after the prefix. Messages that already carry the phrase are left untouched.