Skip to content

v3.4.1

Choose a tag to compare

@its-miso its-miso released this 07 Oct 22:28
· 533 commits to main since this release

One fix, but a subtle one about who owns the retry budget.

#987 taught the model transport to stop retrying permanently-failed requests (403 exits immediately instead of walking the whole ladder) — but the tier layer borrowed the transport's own retry allowlist as its definition of permanence. Any status the transport doesn't itself retry fell through, including transient gateway errors like Cloudflare's 524, which meant a configured ai-primary-retries budget was silently ignored on exactly the errors a retry budget exists for.

  • The tier owns its permanence rule (#1007, closes #1006): only 400/401/403/404 get exactly one tier attempt; everything else — 429, 5xx including 524, network and timeout errors — consumes the configured tier retry budget before fallback. 501 and 507 are pinned tier-retryable, and tests assert 524 stays out of the transport's own set so the two policies can't silently re-merge.
  • Unchanged: 429/500 behavior, and the non-retryable annotation still fires only on the four permanent statuses.

Full changelog: v3.4.0...v3.4.1

Generated changelog (release-please)

Bug Fixes