Skip to content

chore(node): upgrade Node.js Version to v24.18.0#3023

Merged
gardener-prow[bot] merged 1 commit into
masterfrom
renovate/node-version
Jun 26, 2026
Merged

chore(node): upgrade Node.js Version to v24.18.0#3023
gardener-prow[bot] merged 1 commit into
masterfrom
renovate/node-version

Conversation

@gardener-ci-robot

@gardener-ci-robot gardener-ci-robot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
node (source) engines minor 24.16.024.18.0
node final minor 24.16.0-alpine3.2324.18.0-alpine3.23

Release Notes

nodejs/node (node)

v24.18.0: 2026-06-23, Version 24.18.0 'Krypton' (LTS), @​richardlau prepared by @​sxa

Compare Source

Notable Changes
  • [e07e7a31e1] - crypto: update root certificates to NSS 3.123.1 (Node.js GitHub Bot) #​63527
  • [44c8ebcbd6] - http: avoid stream listeners on idle agent sockets (Matteo Collina) #​64004
  • [d3ef4122ee] - (SEMVER-MINOR) buffer: increase Buffer.poolSize default to 64 KiB (Matteo Collina) #​63597
  • [bb2857b85a] - (SEMVER-MINOR) crypto: align key argument names in docs and error messages (Filip Skokan) #​62527
  • [b9d5e87880] - (SEMVER-MINOR) crypto: accept key data in crypto.diffieHellman() and cleanup DH jobs (Filip Skokan) #​62527
  • [ccd756d61e] - (SEMVER-MINOR) crypto: add TurboSHAKE and KangarooTwelve Web Cryptography algorithms (Filip Skokan) #​62183
  • [4c9251fc09] - (SEMVER-MINOR) http: add writeInformation to send arbitrary 1xx status codes (Tim Perry) #​63155
  • [8c989ec4a3] - (SEMVER-MINOR) inspector: expose precise coverage start to JS runtime (sangwook) #​63079
  • [3f54c8ba32] - Revert "stream: noop pause/resume on destroyed streams" (Stewart X Addison) #​63834
Commits

v24.17.0: 2026-06-18, Version 24.17.0 'Krypton' (LTS), @​aduh95

Compare Source

This is a security release.

Notable Changes
  • (CVE-2026-48618) tls: normalize hostname for server identity checks (Matteo Collina) – High
  • (CVE-2026-48933) crypto: guard WebCrypto cipher output length (Filip Skokan) – High
  • (CVE-2026-48615) lib,test: redact proxy credentials in tunnel errors (Matteo Collina) – Medium
  • (CVE-2026-48619) http2: cap originSet size to prevent unbounded memory growth (Matteo Collina) – Medium
  • (CVE-2026-48928) tls: fix case-sensitive SNI context matching (Matteo Collina) – Medium
  • (CVE-2026-48930) dns,net: reject hostnames with embedded NUL bytes (Matteo Collina) – Medium
  • (CVE-2026-48934) tls: bind reusable sessions to authenticated host (Matteo Collina) – Medium
  • (CVE-2026-48937) deps: fix integration issues with the latest nghttp2 – Medium
  • (CVE-2026-48617) permission: handle process.chdir on writereport (RafaelGSS) – Low
  • (CVE-2026-48931) http: fix response queue poisoning in http.Agent (Matteo Collina) – Low
  • (CVE-2026-48935) permission: disable FileHandle utimes with permission model (RafaelGSS) – Low
Commits

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 becomes conflicted, 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 has been generated by Mend Renovate.

@gardener-ci-robot gardener-ci-robot added kind/enhancement Enhancement, improvement, extension renovate labels Jun 18, 2026
@gardener-ci-robot gardener-ci-robot added kind/enhancement Enhancement, improvement, extension renovate labels Jun 18, 2026
@coderabbitai

coderabbitai Bot commented Jun 18, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e50f6e8d-9ba6-4442-960d-0bfd33ef59cf

📥 Commits

Reviewing files that changed from the base of the PR and between 3e399cf and f62c839.

📒 Files selected for processing (12)
  • Dockerfile
  • backend/package.json
  • charts/package.json
  • frontend/package.json
  • package.json
  • packages/kube-client/package.json
  • packages/kube-config/package.json
  • packages/logger/package.json
  • packages/monitor/package.json
  • packages/polling-watcher/package.json
  • packages/request/package.json
  • packages/test-utils/package.json
✅ Files skipped from review due to trivial changes (7)
  • backend/package.json
  • packages/logger/package.json
  • packages/polling-watcher/package.json
  • charts/package.json
  • packages/kube-client/package.json
  • packages/kube-config/package.json
  • packages/monitor/package.json
🚧 Files skipped from review as they are similar to previous changes (5)
  • packages/test-utils/package.json
  • package.json
  • Dockerfile
  • packages/request/package.json
  • frontend/package.json

📝 Walkthrough

Walkthrough

The Docker builder image and all listed package manifests update their Node.js version requirement from 24.16.0 to 24.18.0.

Changes

Node.js Engine Version Bump

Layer / File(s) Summary
Docker builder image bump
Dockerfile
The builder stage base image tag changes from node:24.16.0-alpine3.23 to node:24.18.0-alpine3.23.
engines.node bump across all packages
package.json, backend/package.json, frontend/package.json, charts/package.json, packages/kube-client/package.json, packages/kube-config/package.json, packages/logger/package.json, packages/monitor/package.json, packages/polling-watcher/package.json, packages/request/package.json, packages/test-utils/package.json
The engines.node field is updated from 24.16.0 to 24.18.0 across the repository’s package manifests.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested labels

size/M

Suggested reviewers

  • grolu
  • holgerkoser
  • klocke-io
  • petersutter

Poem

🐇 Hop, hop, the Node got new spring,
24.18 now in everything.
Manifests wink, Dockerfile too,
A tiny version nudge hopped through.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description is Renovate-generated and does not follow the repository's required PR template sections or fields. Add the template sections: /area, /kind, What this PR does, fixes, special notes, and the required release note block.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely describes the main change: upgrading Node.js to v24.18.0.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch renovate/node-version

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@gardener-prow gardener-prow Bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. cla: yes Indicates the PR's author has signed the cla-assistant.io CLA. labels Jun 18, 2026

@coderabbitai coderabbitai 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.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Line 48: The Node version specified in the GitHub workflow file
.github/workflows/build.yaml does not match the engine requirement in
package.json. Update the setup-node action configuration in
.github/workflows/build.yaml to use Node version 24.17.0 instead of 24.16.0 in
both occurrences (the two places where setup-node is configured). This ensures
the CI pipeline validates the code against the same Node runtime version
specified in package.json.

In `@packages/test-utils/package.json`:
- Line 34: Update all Node.js version references from 24.16.0 to 24.17.0 across
the CI/Docker infrastructure to match the engines constraint now enforced in
package.json files. Specifically, replace 24.16.0 with 24.17.0 in
.github/workflows/build.yaml (both instances), Dockerfile, and
.github/actions/prepare-release/action.yaml to ensure yarn install will succeed
with the new Node version requirement enforced by yarn.config.cjs.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7f03dfcb-2ca4-407d-8b7e-5691eaf5260f

📥 Commits

Reviewing files that changed from the base of the PR and between 404da27 and a54a27b.

📒 Files selected for processing (11)
  • backend/package.json
  • charts/package.json
  • frontend/package.json
  • package.json
  • packages/kube-client/package.json
  • packages/kube-config/package.json
  • packages/logger/package.json
  • packages/monitor/package.json
  • packages/polling-watcher/package.json
  • packages/request/package.json
  • packages/test-utils/package.json

Comment thread package.json Outdated
Comment thread packages/test-utils/package.json Outdated
"packageManager": "[email protected]",
"engines": {
"node": "24.16.0"
"node": "24.17.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify Node version consistency across CI/CD and build files.

# Test 1: Check CI workflow node-version
echo "=== CI Workflow Node Version ==="
rg 'node-version' .github/workflows/build.yaml -A 1 -B 1

# Test 2: Check Dockerfile node versions
echo "=== Dockerfile Node Versions ==="
rg 'FROM node:' Dockerfile -A 1 -B 1

# Test 3: Check for any other Node version pins in CI configs
echo "=== Other CI Config Node Versions ==="
rg 'node.*24\.16\.0|24\.17\.0' .github/ --type yaml --type json -C 2

Repository: gardener/dashboard

Length of output: 1875


🏁 Script executed:

#!/bin/bash
# Find all package.json files and check their engines.node constraint

echo "=== All package.json files with engines.node values ==="
fd 'package\.json$' | while read f; do
  if grep -q '"engines"' "$f" 2>/dev/null; then
    echo "File: $f"
    rg -A 2 '"engines"' "$f"
    echo "---"
  fi
done

# Specifically check root package.json
echo ""
echo "=== Root package.json full content (first 50 lines) ==="
head -50 package.json

Repository: gardener/dashboard

Length of output: 2578


Node.js version mismatch between package.json and CI/Docker infrastructure.

All engines.node constraints have been updated to 24.17.0 across the monorepo (root and 10 workspace packages), but the CI workflow (.github/workflows/build.yaml), Docker build (.Dockerfile), and release action (.github/actions/prepare-release/action.yaml) still reference 24.16.0. Since yarn.config.cjs enforces the engines constraint across all workspaces, yarn install will fail in CI and Docker builds attempting to use Node 24.16.0 against the 24.17.0 requirement.

Update the following to use Node 24.17.0:

  • .github/workflows/build.yaml (two instances)
  • Dockerfile
  • .github/actions/prepare-release/action.yaml
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/test-utils/package.json` at line 34, Update all Node.js version
references from 24.16.0 to 24.17.0 across the CI/Docker infrastructure to match
the engines constraint now enforced in package.json files. Specifically, replace
24.16.0 with 24.17.0 in .github/workflows/build.yaml (both instances),
Dockerfile, and .github/actions/prepare-release/action.yaml to ensure yarn
install will succeed with the new Node version requirement enforced by
yarn.config.cjs.

@gardener-ci-robot gardener-ci-robot force-pushed the renovate/node-version branch 2 times, most recently from 342c409 to 3e399cf Compare June 23, 2026 23:38
@gardener-ci-robot gardener-ci-robot changed the title chore(node): upgrade Node.js Version to v24.17.0 chore(node): upgrade Node.js Version Jun 23, 2026

@coderabbitai coderabbitai 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.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@backend/package.json`:
- Line 105: The engines.node version is inconsistent across configuration files.
Update the engines.node field in package.json files to match the Node.js version
used in CI workflows and Docker, or vice versa. Choose either 24.17.0 or 24.18.0
and apply this version consistently across the engines.node specification in
package.json, the Node image version in Dockerfile, and the node-version in CI
workflow files to ensure yarn install succeeds and pipeline execution is not
interrupted.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b262cea8-527d-4ada-8f01-c935ca1e73aa

📥 Commits

Reviewing files that changed from the base of the PR and between a54a27b and 3e399cf.

📒 Files selected for processing (12)
  • Dockerfile
  • backend/package.json
  • charts/package.json
  • frontend/package.json
  • package.json
  • packages/kube-client/package.json
  • packages/kube-config/package.json
  • packages/logger/package.json
  • packages/monitor/package.json
  • packages/polling-watcher/package.json
  • packages/request/package.json
  • packages/test-utils/package.json
✅ Files skipped from review due to trivial changes (7)
  • packages/kube-client/package.json
  • packages/polling-watcher/package.json
  • frontend/package.json
  • Dockerfile
  • packages/logger/package.json
  • packages/monitor/package.json
  • package.json
🚧 Files skipped from review as they are similar to previous changes (1)
  • packages/kube-config/package.json

Comment thread backend/package.json
"packageManager": "[email protected]",
"engines": {
"node": "24.16.0"
"node": "24.18.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🩺 Stability & Availability | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify Node version contract drift across manifests and execution environments.

set -eu

echo "== engines.node values =="
fd -a 'package.json$' . | while read -r f; do
  awk '
    /"engines"[[:space:]]*:/,/\}/ {
      if ($0 ~ /"node"[[:space:]]*:/) {
        gsub(/^[[:space:]]+/, "", $0);
        printf "%s -> %s\n", FILENAME, $0
      }
    }
  ' "$f"
done

echo
echo "== CI setup-node pins =="
rg -n --type=yaml "node-version:\s*'?[0-9]+\.[0-9]+\.[0-9]+'?" .github/workflows

echo
echo "== Docker Node base image pins =="
rg -n "FROM node:[0-9]+\.[0-9]+\.[0-9]+-alpine" Dockerfile .github/actions -g '*.yaml' -g '*.yml'

Repository: gardener/dashboard

Length of output: 1173


Align engines.node with CI/Docker runtime versions.

engines.node is pinned to 24.18.0 across all package.json files, but CI (.github/workflows/build.yaml lines 89, 119) and Docker (Dockerfile line 6) use 24.17.0. This version mismatch can cause yarn install to fail with strict engine enforcement and break pipeline execution. Update either all engines.node entries to 24.17.0 or upgrade CI and Docker to 24.18.0.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@backend/package.json` at line 105, The engines.node version is inconsistent
across configuration files. Update the engines.node field in package.json files
to match the Node.js version used in CI workflows and Docker, or vice versa.
Choose either 24.17.0 or 24.18.0 and apply this version consistently across the
engines.node specification in package.json, the Node image version in
Dockerfile, and the node-version in CI workflow files to ensure yarn install
succeeds and pipeline execution is not interrupted.

@gardener-ci-robot gardener-ci-robot changed the title chore(node): upgrade Node.js Version chore(node): upgrade Node.js Version to v24.18.0 Jun 24, 2026

@petersutter petersutter left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

/lgtm
/approve

@gardener-prow gardener-prow Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 26, 2026
@gardener-prow

gardener-prow Bot commented Jun 26, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: petersutter

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@gardener-prow

gardener-prow Bot commented Jun 26, 2026

Copy link
Copy Markdown

LGTM label has been added.

DetailsGit tree hash: 2ea55f9c4e80d34fa9efbdd7e8d5cf1e10e09116

@gardener-prow gardener-prow Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 26, 2026
@gardener-prow gardener-prow Bot merged commit 010a3a5 into master Jun 26, 2026
52 of 64 checks passed
@gardener-prow gardener-prow Bot deleted the renovate/node-version branch June 26, 2026 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Indicates the PR's author has signed the cla-assistant.io CLA. kind/enhancement Enhancement, improvement, extension lgtm Indicates that a PR is ready to be merged. renovate size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants