-
-
Notifications
You must be signed in to change notification settings - Fork 2
Upgrade Node.js to v22 in CI workflows #882
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -22,7 +22,7 @@ jobs: | |||||
| - name: Setup Node.js | ||||||
| uses: actions/setup-node@v6 | ||||||
| with: | ||||||
| node-version: '20' | ||||||
| node-version: '22' | ||||||
|
||||||
| node-version: '22' | |
| node-version: '22.12.0' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Astro v6 requires Node.js >= 22.12.0 (per PR description).
node-version: "22"only pins the major and can resolve to an earlier 22.x release depending on what setup-node selects, which could reintroduce the build failure. Consider pinning to at least22.12.0(or22.12.x) to enforce the minimum supported version deterministically.