chore(deps): update dependency node to v24 - #20
Conversation
751a961 to
3c66119
Compare
3c66119 to
e28cf9e
Compare
e28cf9e to
4a6244b
Compare
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| - uses: actions/setup-node@v4 | ||
| with: | ||
| node-version: 20 | ||
| node-version: 24 |
There was a problem hiding this comment.
[HIGH] correctness
Node.js version 24 is not currently a stable release and is likely unavailable via actions/setup-node, causing the CI workflow to fail.
💡 Use a supported version such as '20' (LTS) or '22' (Current). Alternatively, use 'node-version-file: .nvmrc' to sync with project configuration.
| - uses: actions/setup-node@v4 | ||
| with: | ||
| node-version: 22 | ||
| node-version: 24 |
There was a problem hiding this comment.
[HIGH] correctness
Node.js version 24 is not currently a stable release and is likely unavailable via actions/setup-node, causing the release workflow to fail.
💡 Use a supported version such as '20' (LTS) or '22' (Current). Alternatively, use 'node-version-file: .nvmrc' to sync with project configuration.
There was a problem hiding this comment.
AI Code Review ❌
Found 2 finding(s):
HIGH (2)
.github/workflows/ci.yml:56— Node.js version 24 is not currently a stable release and is likely unavailable via actions/setup-node, causing the CI workflow to fail..github/workflows/release.yml:29— Node.js version 24 is not currently a stable release and is likely unavailable via actions/setup-node, causing the release workflow to fail.
4a6244b to
eb6bdd8
Compare
| - uses: actions/setup-node@v4 | ||
| with: | ||
| node-version: 20 | ||
| node-version: 24 |
There was a problem hiding this comment.
[HIGH] correctness
Upgraded Node.js from 20 to 24 (Current release) in CI. This removes testing coverage for Node 20 (Maintenance LTS) and introduces instability risks as dependencies may not yet support Node 24.
💡 Consider using a matrix strategy to test against multiple Node versions (e.g., 20, 22, and 24) or switch to Node 22 (Active LTS) to ensure stability while maintaining ecosystem compatibility.
| - uses: actions/setup-node@v4 | ||
| with: | ||
| node-version: 22 | ||
| node-version: 24 |
There was a problem hiding this comment.
[HIGH] correctness
Upgraded Node.js from 22 to 24 (Current release) for releases. Publishing using a non-LTS version increases the risk of environment-specific failures and may produce artifacts incompatible with environments running Node 22.
💡 Revert to Node 22 (Active LTS) for the release workflow to ensure the publishing process runs on the most stable and widely supported platform.
There was a problem hiding this comment.
AI Code Review ❌
Found 2 finding(s):
HIGH (2)
.github/workflows/ci.yml:56— Upgraded Node.js from 20 to 24 (Current release) in CI. This removes testing coverage for Node 20 (Maintenance LTS) and introduces instability risks as dependencies may not yet support Node 24..github/workflows/release.yml:29— Upgraded Node.js from 22 to 24 (Current release) for releases. Publishing using a non-LTS version increases the risk of environment-specific failures and may produce artifacts incompatible with environments running Node 22.
eb6bdd8 to
3ed8cd3
Compare
3ed8cd3 to
714f8c4
Compare
213a69a to
4d54f00
Compare
| - uses: actions/setup-node@v4 | ||
| with: | ||
| node-version: 20 | ||
| node-version: 24 |
There was a problem hiding this comment.
[HIGH] correctness
Node.js version 24 is not an official stable release and is likely not supported by actions/setup-node, which will cause the CI workflow to fail.
💡 Verify the intended Node.js version. Use Node 20 (Active LTS) or Node 22 (Current).
| - uses: actions/setup-node@v4 | ||
| with: | ||
| node-version: 22 | ||
| node-version: 24 |
There was a problem hiding this comment.
[HIGH] correctness
Node.js version 24 is not an official stable release and is likely not supported by actions/setup-node, which will cause the release workflow to fail.
💡 Verify the intended Node.js version. Use Node 20 (Active LTS) or Node 22 (Current).
There was a problem hiding this comment.
AI Code Review ❌
Found 2 finding(s):
HIGH (2)
.github/workflows/ci.yml:56— Node.js version 24 is not an official stable release and is likely not supported by actions/setup-node, which will cause the CI workflow to fail..github/workflows/release.yml:29— Node.js version 24 is not an official stable release and is likely not supported by actions/setup-node, which will cause the release workflow to fail.
4d54f00 to
a40ea85
Compare
| - uses: actions/setup-node@v7 | ||
| with: | ||
| node-version: 20 | ||
| node-version: 24 |
There was a problem hiding this comment.
[HIGH] correctness
Invalid Node.js version specified. Version 24 is not a stable release yet and will likely cause the actions/setup-node step to fail.
💡 Use a valid Node.js version such as '20' (LTS) or '22' (Current). Alternatively, use 'lts/*' to automatically use the latest LTS version.
| - uses: actions/setup-node@v7 | ||
| with: | ||
| node-version: 22 | ||
| node-version: 24 |
There was a problem hiding this comment.
[HIGH] correctness
Invalid Node.js version specified. Version 24 is not a stable release yet and will likely cause the actions/setup-node step to fail.
💡 Use a valid Node.js version such as '20' (LTS) or '22' (Current). For release workflows, it is recommended to pin to an LTS version for stability.
There was a problem hiding this comment.
AI Code Review ❌
Found 2 finding(s):
HIGH (2)
.github/workflows/ci.yml:56— Invalid Node.js version specified. Version 24 is not a stable release yet and will likely cause the actions/setup-node step to fail..github/workflows/release.yml:29— Invalid Node.js version specified. Version 24 is not a stable release yet and will likely cause the actions/setup-node step to fail.
a40ea85 to
eb274f0
Compare
| - uses: actions/setup-node@v7 | ||
| with: | ||
| node-version: 22 | ||
| node-version: 24 |
There was a problem hiding this comment.
[HIGH] correctness
Using non-LTS Node.js version (24) in the release workflow poses stability risks.
💡 Use an Active LTS version (e.g., Node 22) for production releases to ensure compatibility and stability for downstream consumers, unless the library explicitly requires Node 24 features.
eb274f0 to
bb280a0
Compare
bb280a0 to
91ef73b
Compare
91ef73b to
2bc7c7e
Compare
This PR contains the following updates:
22→2420→24Release Notes
actions/node-versions (node)
v24.20.0: 24.20.0Compare Source
Node.js 24.20.0
v24.19.0: 24.19.0Compare Source
Node.js 24.19.0
v24.18.1: 24.18.1Compare Source
Node.js 24.18.1
v24.18.0: 24.18.0Compare Source
Node.js 24.18.0
v24.17.0: 24.17.0Compare Source
Node.js 24.17.0
v24.16.0: 24.16.0Compare Source
Node.js 24.16.0
v24.15.0: 24.15.0Compare Source
Node.js 24.15.0
v24.14.1: 24.14.1Compare Source
Node.js 24.14.1
v24.14.0: 24.14.0Compare Source
Node.js 24.14.0
v24.13.1: 24.13.1Compare Source
Node.js 24.13.1
v24.13.0: 24.13.0Compare Source
Node.js 24.13.0
v24.12.0: 24.12.0Compare Source
Node.js 24.12.0
v24.11.1: 24.11.1Compare Source
Node.js 24.11.1
v24.11.0: 24.11.0Compare Source
Node.js 24.11.0
v24.10.0: 24.10.0Compare Source
Node.js 24.10.0
v24.9.0: 24.9.0Compare Source
Node.js 24.9.0
v24.8.0: 24.8.0Compare Source
Node.js 24.8.0
v24.7.0: 24.7.0Compare Source
Node.js 24.7.0
v24.6.0: 24.6.0Compare Source
Node.js 24.6.0
v24.5.0: 24.5.0Compare Source
Node.js 24.5.0
v24.4.1: 24.4.1Compare Source
Node.js 24.4.1
v24.4.0: 24.4.0Compare Source
Node.js 24.4.0
v24.3.0: 24.3.0Compare Source
Node.js 24.3.0
v24.2.0: 24.2.0Compare Source
Node.js 24.2.0
v24.1.0: 24.1.0Compare Source
Node.js 24.1.0
v24.0.2: 24.0.2Compare Source
Node.js 24.0.2
v24.0.1: 24.0.1Compare Source
Node.js 24.0.1
v24.0.0: 24.0.0Compare Source
Node.js 24.0.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.