Repository navigation
ci: migrate docs deploy workflow to Node 24 - #19
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
Fix the Documentation workflow after GitHub Actions moved JavaScript actions to Node 24 by default.
Changes
actions/checkout@v4->@v5actions/setup-node@v4->@v5actions/upload-artifact@v4->@v6actions/download-artifact@v4->@v7cloudflare/wrangler-action@v3->@v4Why
cloudflare/wrangler-action@v3still used the Node 20 action runtime and defaulted to Wrangler 3.90.0. Under the current GitHub-hosted runner behavior, that action is forced onto Node 24 and fails during itsnpx --no-install wrangler --versionprobe before deployment. Cloudflare's v4 action is the Node 24-compatible path and defaults to Wrangler v4.No application/runtime code changes.