Skip to content

chore: version packages#413

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

chore: version packages#413
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

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_limited failure messages so post-content OpenAI-compatible
    clients 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-compatible
    collapses an in-band {error:{...}} chunk to just its message string — so its
    retry heuristic classifies on the message text alone. That heuristic keys on the
    literal phrases "rate limit" / "too many requests", but normalizeTaskFailError
    classifies rate limits more broadly (a bare 429, rate-limited with a hyphen,
    or rate_limit with an underscore). A genuine rate limit whose upstream text
    lacked the exact phrase therefore would not trigger the client's auto-retry.

    normalizeTaskFailError now prefixes such messages with rate limit: when the
    final code is rate_limited and the phrase is absent. This is an honest
    translation, 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants