Repository navigation
fix(web): give the Worker the GitHub token for the releases feed - #1129
Merged
Merged
Conversation
Sync PERSONAL_ACCESS_TOKEN to the web Worker on deploy so /github-releases.json (and sponsors) call the GitHub API authenticated instead of hitting the shared unauthenticated limit on Cloudflare IPs. Switch the releases feed back from Atom to the REST API, which also filters drafts and prereleases. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 12 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
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
1 participant
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.
Follow-up to #1128.
deploy-web.yml: on regular deploys,wrangler secret put PERSONAL_ACCESS_TOKENfrom the repo secret (same step that removes legacy secrets). Secrets persist into A/B uploaded versions, so the split path needs nothing.Cap-go/capgo.app+Cap-go/capacitor-updater./sponsorsalready readenv.PERSONAL_ACCESS_TOKENbut the Worker never had it, so that endpoint starts working too.Test:
bun test apps/web/test/github-releases.test.jspass,astro check0 errors.🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.