-
-
Notifications
You must be signed in to change notification settings - Fork 41
Change worker account #126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
simonabadoiu
wants to merge
4
commits into
master
Choose a base branch
from
change-worker-account
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
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
MattIPv4
previously approved these changes
Feb 5, 2026
5216e69 to
420d006
Compare
420d006 to
9ce2a1e
Compare
9ce2a1e to
2f58ceb
Compare
2f58ceb to
fc6485f
Compare
fc6485f to
03fb2c2
Compare
- Add account_id to main configuration - Remove default KV namespace binding - Update staging KV namespace ID - Update production KV namespace ID - Remove route configurations from staging and production environments
- Replace CLOUDFLARE_API_TOKEN_PRODUCTION with CLOUDFLARE_CDNJS_ACCOUNT_ID in production workflow - Replace CLOUDFLARE_ACCOUNT_ID_PRODUCTION with CLOUDFLARE_CDNJS_ACCOUNT_ID in production workflow - Replace CLOUDFLARE_API_TOKEN_STAGING with CLOUDFLARE_CDNJS_ACCOUNT_ID in staging workflow - Replace CLOUDFLARE_ACCOUNT_ID_STAGING with CLOUDFLARE_CDNJS_ACCOUNT_ID in staging workflow
- Replace CLOUDFLARE_CDNJS_ACCOUNT_ID with CLOUDFLARE_CDNJS_API_TOKEN for CLOUDFLARE_API_TOKEN in production workflow - Replace CLOUDFLARE_CDNJS_ACCOUNT_ID with CLOUDFLARE_CDNJS_API_TOKEN for CLOUDFLARE_API_TOKEN in staging workflow
03fb2c2 to
6bd23c9
Compare
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.
Type of Change
What issue does this relate to?
Migration to unified cdnjs Cloudflare account credentials. And move to another cf account
What should this PR do?
What are the acceptance criteria?