Skip to content

Conversation

@MikeMcC399
Copy link
Contributor

@MikeMcC399 MikeMcC399 commented Feb 1, 2026

Refs: #2264

Description

Deprecation information for (un)bundling of Yarn v1 Classic is added to the README.

Users with legacy needs are also advised that Yarn v1 can be installed with the following commands, according to Yarn installation instructions:

npm install --global yarn

This is possible, since Node.js bundles the npm package manager and so provides the prerequisites to use npm to install Yarn v1.

Motivation and Context

  • Node.js Docker images bundle the Yarn v1 Classic package manager into each published image. This has been the case since Feb 2017
  • Yarn v1 Classic package manager has been frozen since the release of Yarn 2 in January 2020 and is unsupported since then.
  • https://yarnpkg.com/latest-version has remained at release yarn@1.22.22 since March 2024 in line with the frozen and unsupported status of this version
  • Removal of Yarn v1 from Node.js Docker images has been proposed again and again over the years
  • Yarn is not included in the Node.js distribution itself and so it is an exceptional addition into the Docker images

Assumption

According to the discussion in #2264 it's assumed here that Node.js Docker images will stop bundling Yarn v1 for Node.js release lines 26 and above, starting with the release of Node.js 26.0.0 (planned for 2026-04-22).

It's also assumed that Yarn v1 will continue to be bundled with currently supported Node.js release lines for legacy reasons. The end of availability of Docker images with Yarn v1 would then be when Node.js 24.x transitions into end-of-life planned for 2028-04-30.

Testing Details

N/A

Example Output(if appropriate)

N/A

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. See PR Replace broken Docker Badge #2367 for fix to Markdown link check workflow

    [✖] https://dockerico.blankenship.io/image/node → Status: 404
    ERROR: 1 dead link found in ./README.md !

@MikeMcC399
Copy link
Contributor Author

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.

1 participant