Skip to content
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

Update CI to use node 22 @W-16170810@ #178

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

joeluong-sfcc
Copy link
Contributor

@joeluong-sfcc joeluong-sfcc commented Jan 13, 2025

This PR updates the publish and test workflows to use node 22

This PR also switches the bundlesize package for the bundlesize2 package as yarn install was failing due to a transitive dependency iltorb in bundlesize that is not supported in newer node versions.

There will be a follow up PR in the future to remove old node versions from the CI when we drop official support for them.

NOTE: we're holding off on merging this until bundlesize2 is approved as a 3PP

@joeluong-sfcc joeluong-sfcc marked this pull request as ready for review January 13, 2025 18:03
@joeluong-sfcc joeluong-sfcc requested a review from a team as a code owner January 13, 2025 18:03
Copy link

@unandyala unandyala left a comment

Choose a reason for hiding this comment

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

LGTM

@@ -9,7 +9,8 @@ jobs:
linux-tests:
strategy:
matrix:
node: [12, 14, 16, 18]
# TODO: remove older versions of node
node: [12, 14, 16, 18, 20, 22]

Choose a reason for hiding this comment

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

Just curious - Is there a specific reason why we want to remove older node versions ins a separate PR?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, the plan is to remove the older node versions when we drop official support for them, which is a breaking change, so we plan to remove them in the next major version most likely when we release the OAS SDK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants