Skip to content

chore: bump node to 24.22.1 - #1979

Merged
LautaroPetaccio merged 1 commit into
mainfrom
chore/node-24.22.1
Oct 21, 2026
Merged

LautaroPetaccio merged 1 commit into
mainfrom
chore/node-24.22.1

Conversation

@LautaroPetaccio

Copy link
Copy Markdown
Contributor

Bumps the Node base image in Dockerfile (single stage) to Node 24.22.1.

  • Update the node:24-alpine digest from 24.18.0 to 24.22.1 (Alpine 3.24).
  • Distro is unchanged (Alpine 3.24); Node major stays 24.
  • CI validates the build.

Update the node:24-alpine digest from 24.18.0 to 24.22.1 (Alpine 3.24).

@decentraland-bot decentraland-bot left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Review: chore: bump node to 24.22.1

Verdict: Approve. No P0, P1 or P2 findings.

The base stage moves from 24.18.0 (sha256:a0b9bf06…) to sha256:6a1c190e… (24.22.1-alpine3.24).

Checks performed

  • The new digest is the official Docker Hub library/node multi-arch index for Node 24.22.1, cross-checked against both the floating tag and the explicit 24.22.1-* tag.
  • The distro family is unchanged (Alpine 3.24 → 3.24), so the Dockerfile's package installs and any native modules are unaffected.
  • Every other Node pin in the repo (.nvmrc, engines, CI setup-node) is major-only or updated in this PR, so none conflict.
  • CI is green. The title follows the semantic format and the branch name chore/node-24.22.1 matches ADR-6.
  • No public API surface changes, so consumer-impact analysis does not apply.

Reviewed by Jarvis 🤖 · Requested by Lautaro Petaccio (<@U025WCHLMN3>) via Slack

@LautaroPetaccio
LautaroPetaccio merged commit a416565 into main Oct 21, 2026
4 checks passed
@LautaroPetaccio
LautaroPetaccio deleted the chore/node-24.22.1 branch October 21, 2026 18:59
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.

2 participants