Improve i18n retry logic for rate-limited requests (HTTP 429)#53
Merged
Improve i18n retry logic for rate-limited requests (HTTP 429)#53
Conversation
dpanta94
reviewed
Feb 20, 2026
dpanta94
reviewed
Feb 20, 2026
dpanta94
approved these changes
Feb 20, 2026
d4mation
added a commit
that referenced
this pull request
Feb 23, 2026
Replace parallel Promise.all downloads with sequential batch processing and add smarter HTTP 429 rate-limit handling with exponential backoff. - Add --delay and --batch-size CLI options - Clamp --retries to 1-5 range - Use backoff multipliers [16, 31, 91, 151] for 429 responses - Respect Retry-After header capped to backoff schedule - Extract saveTranslationFile helper - Add User-Agent header to all fetch requests - Track failed downloads and return exit code 1 on any failure - Add 429 recovery and exhaustion tests
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
2 participants
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.
Improve the pup i18n command’s retry behavior when hitting WordPress.org rate limits (HTTP 429).
Previously, retries treated all failures the same, which could cause repeated rapid requests during rate limiting. This update introduces smarter handling for 429 responses while keeping the original retry flow intact for all other errors.