Skip to content

chore(deps): update dependency node to v24 - #20

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/node-24.x
Open

chore(deps): update dependency node to v24#20
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/node-24.x

Conversation

@renovate

@renovate renovate Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
node uses-with major 2224
node uses-with major 2024

Release Notes

actions/node-versions (node)

v24.19.0: 24.19.0

Compare Source

Node.js 24.19.0

v24.18.1: 24.18.1

Compare Source

Node.js 24.18.1

v24.18.0: 24.18.0

Compare Source

Node.js 24.18.0

v24.17.0: 24.17.0

Compare Source

Node.js 24.17.0

v24.16.0: 24.16.0

Compare Source

Node.js 24.16.0

v24.15.0: 24.15.0

Compare Source

Node.js 24.15.0

v24.14.1: 24.14.1

Compare Source

Node.js 24.14.1

v24.14.0: 24.14.0

Compare Source

Node.js 24.14.0

v24.13.1: 24.13.1

Compare Source

Node.js 24.13.1

v24.13.0: 24.13.0

Compare Source

Node.js 24.13.0

v24.12.0: 24.12.0

Compare Source

Node.js 24.12.0

v24.11.1: 24.11.1

Compare Source

Node.js 24.11.1

v24.11.0: 24.11.0

Compare Source

Node.js 24.11.0

v24.10.0: 24.10.0

Compare Source

Node.js 24.10.0

v24.9.0: 24.9.0

Compare Source

Node.js 24.9.0

v24.8.0: 24.8.0

Compare Source

Node.js 24.8.0

v24.7.0: 24.7.0

Compare Source

Node.js 24.7.0

v24.6.0: 24.6.0

Compare Source

Node.js 24.6.0

v24.5.0: 24.5.0

Compare Source

Node.js 24.5.0

v24.4.1: 24.4.1

Compare Source

Node.js 24.4.1

v24.4.0: 24.4.0

Compare Source

Node.js 24.4.0

v24.3.0: 24.3.0

Compare Source

Node.js 24.3.0

v24.2.0: 24.2.0

Compare Source

Node.js 24.2.0

v24.1.0: 24.1.0

Compare Source

Node.js 24.1.0

v24.0.2: 24.0.2

Compare Source

Node.js 24.0.2

v24.0.1: 24.0.1

Compare Source

Node.js 24.0.1

v24.0.0: 24.0.0

Compare Source

Node.js 24.0.0


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/node-24.x branch from 751a961 to 3c66119 Compare August 17, 2026 23:22

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

AI Code Review ✅

No issues found. LGTM!

@renovate
renovate Bot force-pushed the renovate/node-24.x branch from 3c66119 to e28cf9e Compare August 17, 2026 23:27

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

AI Code Review ✅

No issues found. LGTM!

@renovate
renovate Bot force-pushed the renovate/node-24.x branch from e28cf9e to 4a6244b Compare August 18, 2026 01:15
Comment thread .github/workflows/ci.yml
- uses: actions/setup-node@v4
with:
node-version: 20
node-version: 24

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

[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

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

[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.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

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.

⚠️ Review blocked due to critical/high severity findings.

@renovate
renovate Bot force-pushed the renovate/node-24.x branch from 4a6244b to eb6bdd8 Compare August 18, 2026 07:35
Comment thread .github/workflows/ci.yml
- uses: actions/setup-node@v4
with:
node-version: 20
node-version: 24

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

[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

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

[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.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

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.

⚠️ Review blocked due to critical/high severity findings.

@renovate
renovate Bot force-pushed the renovate/node-24.x branch from eb6bdd8 to 3ed8cd3 Compare August 18, 2026 15:08

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

AI Code Review ✅

No issues found. LGTM!

@renovate
renovate Bot force-pushed the renovate/node-24.x branch from 3ed8cd3 to 714f8c4 Compare August 18, 2026 21:07

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

AI Code Review ✅

No issues found. LGTM!

@renovate
renovate Bot force-pushed the renovate/node-24.x branch 2 times, most recently from 2983a97 to 43f3590 Compare August 19, 2026 07:08
@renovate
renovate Bot force-pushed the renovate/node-24.x branch from 43f3590 to de09dbb Compare August 19, 2026 07:18
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.

0 participants