Add Cloudflare Worker deploy workflow#2
Merged
Conversation
Deploy should follow merges to the default branch instead of requiring a manual wrangler run after code review. The workflow runs tests, injects deployment-only Cloudflare secrets at runtime, and publishes the Worker on pushes to master or main.
avikalpg
commented
May 31, 2026
|
|
||
| - uses: actions/setup-node@v4 | ||
| with: | ||
| node-version: '20' |
Owner
Author
There was a problem hiding this comment.
why use such an old node version instead of the latest LTS version?
Owner
Author
There was a problem hiding this comment.
Good catch. Node 20 is stale here; Node 24 is the current LTS line. Updated both the new deploy workflow and the existing test workflow to use Node 24 so CI and deploy run on the same runtime.
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.
Summary
Verification
Notes
The Worker was also deployed manually from the merged master code before this PR, because the deploy workflow is not live until this PR is merged.