ci(changesets): version packages#1292
Conversation
Deploying voltagent with
|
| Latest commit: |
59ee5e1
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://70ddffde.voltagent.pages.dev |
| Branch Preview URL: | https://changeset-release-main.voltagent.pages.dev |
This comment has been minimized.
This comment has been minimized.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (85)
💤 Files with no reviewable changes (1)
✅ Files skipped from review due to trivial changes (63)
📝 WalkthroughWalkthroughRelease v2.7.5: core version bump and changelog entry for honoring provider Retry-After headers in executeWithModelFallback; all example packages updated to depend on ChangesPatch release v2.7.5: Retry-After header support
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
4e37974 to
59ee5e1
Compare
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
@voltagent/core@2.7.5
Patch Changes
23cc35aThanks @truffle-dev! - Honor the provider'sRetry-Afterheader on retried model calls. The retry loop inexecuteWithModelFallbackpreviously always used local exponential backoff capped at 10 seconds, regardless of what the server asked for; this caused concurrent agents under shared 429/503 contention to converge their retry windows. The delay now usesRetry-After(delta-seconds or HTTP-date, RFC 7231) as a floor, keeps the exponential floor as a backpressure baseline, and caps at 5 minutes for safety.Summary by CodeRabbit
Retry-Afterheader when determining retry delays. The header value serves as a minimum delay floor while maintaining exponential backoff baseline protection, with delays capped at 5 minutes maximum.