security(#239 #240): retry jitter + GitHub Actions hardening#250
Merged
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://white-island-090dfd003-250.westeurope.7.azurestaticapps.net |
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.
Summary
Retry jitter (#239)
claude.jsretry loop used plain exponential backoff — all concurrent clients would retry at the same moment during a 529 overload. Now:min(2^attempt * 1000 + random(0–500ms), 32s).GitHub Actions hardening (#240)
VITE_SUPABASE_ANON_KEY— secret → variableThe Supabase anon key is intentionally public (already ships in the frontend bundle). Storing it as an encrypted secret masked it in CI logs for no benefit. Changed to
vars.VITE_SUPABASE_ANON_KEY.Cleanup-staging
run-nameRemoved
${{ github.event.pull_request.title }}interpolation — PR titles are user-controlled input and should not appear in workflow control fields.Test plan
🤖 Generated with Claude Code