Repository navigation
ci: deploy docs with Wrangler CLI directly - #20
Merged
Merged
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
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
Replace
cloudflare/wrangler-actionin the Documentation deploy job with the repository-pinned Wrangler CLI.Why
The Node 24-compatible
wrangler-action@v4still leaves an extra install/probe layer around Wrangler, and the main-branch deployment is still failing there. The docs package already pinswranglerto4.122.0, so the deploy job can call Wrangler directly and eliminate that failure surface.Changes
cloudflare/wrangler-actionnpx --yes wrangler@4.122.0 pages deploy Wiki/outCLOUDFLARE_API_TOKENandCLOUDFLARE_ACCOUNT_IDthrough Wrangler's standard environment variablesdeployments: writepermissionNo application/runtime code changes.