Skip to content

fix: upgrade Node.js runtime to node24#852

Merged
s3cube merged 3 commits intomasterfrom
node24-upgrade
Mar 25, 2026
Merged

fix: upgrade Node.js runtime to node24#852
s3cube merged 3 commits intomasterfrom
node24-upgrade

Conversation

@s3cube
Copy link
Copy Markdown
Contributor

@s3cube s3cube commented Mar 25, 2026

Issue #, if available:
#845
#846
Description of changes:
Upgrades to Node24

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@s3cube s3cube changed the title Node24 upgrade fix: upgrade Node.js runtime to node24 Mar 25, 2026
- name: Node setup
uses: actions/setup-node@v4
with:
node-version: 24
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Curious why a new Node Setup is need for new version but wan't needed for the existing node version?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Primarily parity with the other action + code-build failures at release-time

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have similar setup in render as well: aws-actions/amazon-ecs-render-task-definition@872f52a

- name: Node setup
uses: actions/setup-node@v4
with:
node-version: 24
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have similar setup in render as well: aws-actions/amazon-ecs-render-task-definition@872f52a

@s3cube s3cube merged commit 8f67c1a into master Mar 25, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants