docs: remove Yarn upgrade/downgrade best practices

[MikeMcC399]

Description

Remove the outdated section Upgrading/downgrading Yarn from the Docker and Node.js Best Practices document.

Motivation and Context

The section describes Upgrading/downgrading Yarn for Node.js 6 and Yarn 1.16.0, referring to an end-of-life Node.js version and the unsupported Yarn v1 Classic module.

Yarn v1 is no longer being bundled for Docker images based on Node.js >=26.

For new Docker images based on Node.js <=25, the Yarn v1 version is set to [email protected] (released March 2024) and is not expected to change. The version itself is frozen and no longer supported.

The instructions can no longer be maintained, since Yarn v1 Classic is now unsupported. The instructions are outdated and only partially work.

In the meantime [email protected] is the most viable Yarn v1 Classic version, so there would be no need to downgrade. It's also the highest version for Yarn v1, so there is nothing to upgrade to, apart from migrating to a higher major version, such as Yarn Modern (v4), which is out-of-scope for this description in any case.

Testing Details

N/A - documentation change only

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.

[sxa]

Hmmm do we really want to remove this completely while it's still applicable for versions of node <26?
Although I guess if there are parts of the instructions that really don't work then it makes sense for a revamp here.

[MikeMcC399]

Theoretically the old node:6 version in the examples could be replaced by a supported version like node:24.

It would however be difficult to find any reasonable Yarn version to use for upgrade / downgrade examples. I wouldn't want to support recommending any user downgrade to a v1 version lower than the current version Yarn 1.22.22, as these all have known problems. The versions to choose from are listed under 1.x releases. I also haven't come across any users in the Yarn v1 repo that have wanted to downgrade. The challenge is to keep Yarn v1 running with the latest version.

There is no newer Yarn v1 version to upgrade to either, so there is no example version that could be used there.

Instructions for migrating to Yarn Modern (v4) shouldn't be part of the Best Practices document here and need to be left to Yarn to document.

My suggestion is still to remove these instructions. I don't believe that attempting to update them would benefit users in practice.