-
Notifications
You must be signed in to change notification settings - Fork 146
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
[DO NOT MERGE] Test node 22 #2133
base: develop
Are you sure you want to change the base?
Changes from 10 commits
d9a7d31
9cf5221
d630de6
c6ed2ae
3f11f2a
6e34877
7d9ab0f
ab17b2e
526b9ee
e3ce49b
f14e69f
bb1bcd5
db16bac
50b556c
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 |
---|---|---|
|
@@ -44,18 +44,15 @@ jobs: | |
strategy: | ||
fail-fast: false | ||
matrix: | ||
node: [16, 18, 20] | ||
npm: [8, 9, 10] | ||
exclude: # node 16 is not compatible with npm 10 | ||
- node: 16 | ||
npm: 10 | ||
node: [20, 22] | ||
npm: [10, 10] | ||
runs-on: ubuntu-latest | ||
env: | ||
# The "default" npm is the one that ships with a given version of node. | ||
# For more: https://nodejs.org/en/download/releases/ | ||
# (We also use this env var for making sure a step runs once for the current node version) | ||
# Note: For node 18, the default was npm 9 until v18.19.0, when it became npm 10 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If we end up moving forward. Don't forget to remove comments about unsupported versions. |
||
IS_DEFAULT_NPM: ${{ (matrix.node == 16 && matrix.npm == 8) || (matrix.node == 18 && matrix.npm == 10) || (matrix.node == 20 && matrix.npm == 10) }} | ||
IS_DEFAULT_NPM: ${{ (matrix.node == 22 && matrix.npm == 10) || (matrix.node == 20 && matrix.npm == 10) }} | ||
# The current recommended version for Managed Runtime: | ||
# https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/upgrade-node-version.html | ||
IS_MRT_NODE: ${{ matrix.node == 20 && matrix.npm == 10 }} | ||
|
@@ -141,18 +138,15 @@ jobs: | |
strategy: | ||
fail-fast: false | ||
matrix: | ||
node: [16, 18, 20] | ||
npm: [8, 9, 10] | ||
exclude: # node 16 is not compatible with npm 10 | ||
- node: 16 | ||
npm: 10 | ||
node: [20, 22] | ||
npm: [10, 10] | ||
runs-on: windows-latest | ||
env: | ||
# The "default" npm is the one that ships with a given version of node. | ||
# For more: https://nodejs.org/en/download/releases/ | ||
# (We also use this env var for making sure a step runs once for the current node version) | ||
# Note: For node 18, the default was npm 9 until v18.19.0, when it became npm 10 | ||
IS_DEFAULT_NPM: ${{ (matrix.node == 16 && matrix.npm == 8) || (matrix.node == 18 && matrix.npm == 10) || (matrix.node == 20 && matrix.npm == 10) }} | ||
IS_DEFAULT_NPM: (matrix.node == 22 && matrix.npm == 10) || (matrix.node == 20 && matrix.npm == 10) }} | ||
# The current recommended version for Managed Runtime: | ||
# https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/upgrade-node-version.html | ||
IS_MRT_NODE: ${{ matrix.node == 20 && matrix.npm == 10 }} | ||
|
@@ -196,7 +190,7 @@ jobs: | |
- name: Setup Node | ||
uses: actions/setup-node@v3 | ||
with: | ||
node-version: 20 | ||
node-version: 22 | ||
|
||
- name: Setup Ubuntu Machine | ||
uses: "./.github/actions/setup_ubuntu" | ||
|
@@ -294,7 +288,7 @@ jobs: | |
- name: Setup Node | ||
uses: actions/setup-node@v3 | ||
with: | ||
node-version: 20 | ||
node-version: 22 | ||
|
||
- name: Setup Windows Machine | ||
uses: "./.github/actions/setup_windows" | ||
|
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -32,7 +32,7 @@ | |
"syncpack": "^10.1.0" | ||
}, | ||
"engines": { | ||
"node": "^16.11.0 || ^18.0.0 || ^20.0.0", | ||
"node": "^16.11.0 || ^18.0.0 || ^20.0.0 || ^22.0.0", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As an aside, I wonder if we should simply adopt nodes support model or a modified version of it, e.g. we only support active node LTS. Then at most we'll probably have 3 versions here. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Although some Node version may be in maintenance but they are still within Life-of-support timeline. IMO, when we do upgrade, we can simply drop the node versions that has no longer support officially. That would also leave us with around 2-3 version here |
||
"npm": "^8.0.0 || ^9.0.0 || ^10.0.0" | ||
}, | ||
"dependencies": { | ||
|
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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.
Node 18 is still in LTS for 5 more months. What is the timeline for this upgrade?
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.
Good call. I believe we have to wait til MRT officially supports Node 22. I think at least one more RP to start this upgrade. I think it is safe to remove 16 for this upgrade since it is already out of support timeline. I'll leave 18 and will remove if it is out of support timeline by time we officially do the upgrade