Skip to content

chore(deps): bump node to 24 in dockerfile - #85

Merged
a-ganguly merged 4 commits into
mainfrom
chore/node-security-bump
Oct 26, 2026
Merged

a-ganguly merged 4 commits into
mainfrom
chore/node-security-bump

Conversation

@piyushsinghgaur1

Copy link
Copy Markdown
Collaborator

Description

Node 16 is end-of-life and no longer receives security patches, so it cannot pick up the fixes in the latest Node.js security release. This moves the Docker build stage from node:16-alpine to node:24-alpine, a supported line with the fix.

How Has This Been Tested?

  • npm ci and npm run build pass on Node 24.22.1
  • Confirmed the node:24-alpine tag exists on Docker Hub

node 16 is end-of-life and has no security patches. move the build stage to node:24-alpine.
use npm ci with the lockfile and skip lifecycle scripts for the production install so resolved versions are pinned.
Comment thread Dockerfile Fixed
npm ci already requires and uses the committed lockfile, so the separate package-lock-only step is not needed.
pin the build image to the exact fixed release instead of the floating 24-alpine tag.
@sonarqubecloud

Copy link
Copy Markdown

@a-ganguly
a-ganguly merged commit d18f6e8 into main Oct 26, 2026
2 of 5 checks passed
@piyushsinghgaur1
piyushsinghgaur1 deleted the chore/node-security-bump branch October 27, 2026 10:01
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.

3 participants