Repository navigation
Version Packages - #126
Merged
Merged
Version Packages#126
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 13, 2026 16:35
a6247ee to
7f4e889
Compare
Pewtro
approved these changes
Oct 13, 2026
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
@blizzard-api/client@5.5.1
Patch Changes
ae53cb3: Update ky to 2.2.0 and delegate 429 retry handling to ky instead of wrapping every request in a custom retry loop.
maxAttemptspreviously compounded with ky's own retries, so a request configured withmaxAttempts: 3sent nine HTTP requests. It now sends exactly three.retryOnRateLimit: falsealso did not stop ky from retrying twice; it now disables retries entirely.Retries are now configured through ky, which also means the token endpoints gain the same
Retry-Afterand rate limit header handling as the resource endpoints, and5xx, network, and timeout failures are retried too. Retry settings passed per request are honoured rather than silently ignored.kyOptions.retryis merged with the client's defaults instead of replacing them, andretryOnRateLimit: falsetakes precedence over it.