Repository navigation
Deploy to Cloudflare from main and release tags - #327
Merged
Merged
Conversation
Every merge to main goes to testnet, and an explorer-v* tag to mainnet. The token is a secret of a GitHub environment only those can use, and Cloudflare's CLI has a lockfile of its own, outside the app's dependencies.
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.
Every merge to
maingoes to testnet, and anexplorer-v*tag goes to mainnet, so nothing reaches mainnet without being on testnet first.CLOUDFLARE_API_TOKENis a secret of thecloudflareGitHub environment, which onlymainandexplorer-v*tags can use, so a workflow changed in a PR can't read it. The job runs on a GitHub-hosted runner.wrangleris pinned on a lockfile of its own indeploy/, outside the app's dependencies, installed without scripts and with signatures checked.Don't merge until the secret is set: the merge itself triggers a testnet deploy.
Tried locally: a clean install, signature check and
wrangler deploy --dry-run.