Skip to content

bump Node.js version to 20.20.1 skipping Yarn and Alpine#2400

Closed
jamsjordn wants to merge 1 commit intonodejs:mainfrom
jamsjordn:version-update
Closed

bump Node.js version to 20.20.1 skipping Yarn and Alpine#2400
jamsjordn wants to merge 1 commit intonodejs:mainfrom
jamsjordn:version-update

Conversation

@jamsjordn
Copy link

Description

Bumps the Node version to 20.20.1 using ./update.sh 20 -s

Motivation and Context

It is the next step in the process to make 20.20.1 available in the docker library. 20.20.0 contains CVE-2025-15467 nodejs/node#61887

Testing Details

Tested locally with

docker build -t node-20-test 20/bookworm/
docker build -t node-20-bookworm-slim-test 20/bookworm-slim/
docker build -t node-20-bullseye-test 20/bullseye/
docker build -t node-20-bullseye-slim-test 20/bullseye-slim/
docker build -t node-20-trixie-test 20/trixie/
docker build -t node-20-trixie-slim-test 20/trixie-slim/

docker run --rm node-20-test node --version
docker run --rm node-20-bookworm-slim-test node --version
docker run --rm node-20-bullseye-test node --version
docker run --rm node-20-bullseye-slim-test node --version
docker run --rm node-20-trixie-test node --version
docker run --rm node-20-trixie-slim-test node --version

Example Output

All outputted v20.20.1

Types of changes

  • Documentation
  • Version change (Update, remove or add more Node.js versions)
  • Variant change (Update, remove or add more variants, or versions of variants)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Other (none of the above)

Checklist

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING.md document.
  • All new and existing tests passed.

@MikeMcC399
Copy link
Contributor

MikeMcC399 commented Mar 6, 2026

@jamsjordn

This gets done automatically. See #2403

@MikeMcC399
Copy link
Contributor

I also realized that the documentation appears to be misleading, so I submitted #2405 to get that sorted out.

@PeterDaveHello
Copy link
Member

Thank you both @jamsjordn @MikeMcC399! As @MikeMcC399 mentioned, we should use #2403 instead, thanks for understanding!

@nschonni nschonni closed this Mar 6, 2026
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.

4 participants