Retry API authentication errors since these can be transient - #3475
Merged
mbg merged 1 commit intoFeb 12, 2026
Merged
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
mbg
approved these changes
Feb 12, 2026
mbg
left a comment
Copy link
Copy Markdown
Member
There was a problem hiding this comment.
This is fine as a short-term improvement.
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
There was a problem hiding this comment.
Pull request overview
Adjusts the shared GitHub API client’s retry configuration to retry certain HTTP status codes associated with transient authentication failures when calling the feature flags API.
Changes:
- Configure Octokit retry plugin to allow retries on 401/403/404 by removing them from doNotRetry.
- Update the API client unit test to assert the new retry configuration.
- Regenerate compiled lib/ outputs to reflect the TypeScript change.
Reviewed changes
Copilot reviewed 14 out of 14 changed files in this pull request and generated 1 comment.
Show a summary per file| File | Description |
|---|---|
| src/api-client.ts | Updates Octokit retry configuration to retry auth-related status codes. |
| src/api-client.test.ts | Updates expectations to include the new retry configuration. |
| lib/upload-sarif-action.js | Generated output update reflecting src/api-client.ts change. |
| lib/upload-sarif-action-post.js | Generated output update reflecting src/api-client.ts change. |
| lib/upload-lib.js | Generated output update reflecting src/api-client.ts change. |
| lib/start-proxy-action.js | Generated output update reflecting src/api-client.ts change. |
| lib/start-proxy-action-post.js | Generated output update reflecting src/api-client.ts change. |
| lib/setup-codeql-action.js | Generated output update reflecting src/api-client.ts change. |
| lib/resolve-environment-action.js | Generated output update reflecting src/api-client.ts change. |
| lib/init-action.js | Generated output update reflecting src/api-client.ts change. |
| lib/init-action-post.js | Generated output update reflecting src/api-client.ts change. |
| lib/autobuild-action.js | Generated output update reflecting src/api-client.ts change. |
| lib/analyze-action.js | Generated output update reflecting src/api-client.ts change. |
| lib/analyze-action-post.js | Generated output update reflecting src/api-client.ts change. |
Sorry, something went wrong.
Comment thread
src/api-client.ts
This was referenced Feb 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
Reviewers
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.
We have observed some transient authentication errors accessing the feature API. As a quick workaround, this PR modifies the retry plugin to retry status codes that can be caused by authentication issues.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Workflow types:
Products:
Environments:
How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist