Prepare Yarn v1 removal in Node.js 26 images #2407

Activity

1. MikeMcC399 commented on Mar 8, 2026

   

   MikeMcC399

   on Mar 8, 2026

   ContributorAuthor

   More actions

   There will be at least one more PR to prepare for Node.js 26, which would involve updating the versions.json to add 26.

   I would suggest creating a new feature branch, for example node-26 to collect and test updates from PRs before they're merged into main. Perhaps one of the regular maintainers could consider that suggestion and create that branch if it sounds like it would be useful?
2. MikeMcC399 commented on Mar 9, 2026

   

   MikeMcC399

   on Mar 9, 2026

   ContributorAuthor

   More actions

   I found multiple issues in the update.sh script when I was looking at possible ways to implement the removal of Yarn:

   • update -s script corrupts Yarn version #2411
   • update -h script help option non-working examples #2412
   • update script misleading log when nothing updated #2413

   It would be cleaner, if these could be addressed first.
3. sxa commented on Mar 16, 2026

   

   sxa

   on Mar 16, 2026

   Last edited by sxa

   Member

   More actions

   FYI @nodejs/docker

   Initial proposed wording for a social media post on this change based on something I posted on Mastodon - comments welcome before it gets submitted to the social team either here ot in the #nodejs-distributions slack channel:

   Starting with the next major release of Node.js (version 26 which is due near the end of April) the "official" container images hosted on dockerhub will no longer include the Yarn V1 package manager which is no longer maintained.

   Since this is a potentially breaking change for some use cases this change will not apply to earlier releases although it will affect anyone who is not pinning to a specific node major version when #NodeJS 26 comes out.

   Ref: https://github.com/nodejs/docker-node/

   (This could be updated to include a reference to the node.js snaps since they may also be removed in v26)
4. MikeMcC399 commented on Mar 16, 2026

   

   MikeMcC399

   on Mar 16, 2026

   ContributorAuthor

   More actions

   Starting with the next major release of Node.js (version 26 which is due near the end of April) the "official" container images hosted on dockerhub will no longer include the Yarn V1 package manager which is no longer maintained.

   That should probably be either the full url https://hub.docker.com/_/node or the name "Docker Hub", although admittedly dockerhub.com does forward to https://hub.docker.com

   (This could be updated to include a reference to the node.js snaps since they may also be removed in v26)

   Pleasingly there has been some reaction and movement in the https://github.com/nodejs/snap repo, and I read that they're planning to remove Yarn in Node.js 25 already. (Node.js 25 is currently missing over there.) But that's really off-topic for here. Just wanted to mention it, since you brought it up!

   👍React with 👍1Reacted by Stewart X Addison
5. nschonni commented on Mar 16, 2026

   

   nschonni

   on Mar 16, 2026

   Member

   More actions

   Thinking out loud, and I'll try and PR something later to update the update.sh:

   if  [ "${nodeVersion:0:2}" -ge "26" ]; then
     sed '/ENV YARN_VERSION/,/rm -rf \/tmp\/\*/ d'
   fi

   Other possible options:

   1. I was thinking about pulling it out or the templates and conditionally adding
   2. Use the same conditional version check in the RUN statement in the templates. I had played with that a little before, but I think some of my line continuations were tripping up the docker build runs.
6. MikeMcC399 commented on Mar 16, 2026

   

   MikeMcC399

   on Mar 16, 2026 · Hidden as outdated

   Author

   show commentMore actions
7. nschonni

   closed this as completedin #2422on Mar 24, 2026
8. icco

   added a commit that references this issue on May 11, 2026

   fix(docker): use corepack for yarn in node:26-slim, bump .nvmrc to 26

   ...

   0fdf34d