#3639 feat(taps): Always retry HTTP 429 errors, regardless of the `extra_retry_statuses` value Pull request opened by edgarrmondragon SSIA Summary by Sourcery Ensure HTTP 429 responses are always treated as retriable errors, regardless of custom retry status configuration. New Features: • Treat HTTP 429 responses as retriable errors independently of the configurable extra retry status list. Enhancements: • Clarify HTTP status code boundaries in validation and metrics logic with explicit code references in comments. meltano/sdk