Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migration to 4.0 is unclear #5849

Open
appsforartists opened this issue Oct 24, 2023 · 12 comments
Open

Migration to 4.0 is unclear #5849

appsforartists opened this issue Oct 24, 2023 · 12 comments
Labels
documentation This issue or pull request is about the documentation

Comments

@appsforartists
Copy link

README > Migration Guide links to "Migrating from 1.x / npm"

It would be helpful to have a guide for upgrading from e.g. 3.x to 4.x, even if it's a brief addition like "Already on a recent version of Yarn? All you need to do is upgrade. Check the changelog to see what's new."

@thorn0
Copy link
Contributor

thorn0 commented Oct 24, 2023

Also adding something like that to the 4.0 blog post might make those users who don't follow the project closely a bit happier.

@milesj
Copy link

milesj commented Oct 24, 2023

This is all I had to do to upgrade from v3.

yarn set version berry
yarn install

It was pretty seamless. yarn install will auto-migrate old things it finds.

@RDIL RDIL self-assigned this Oct 24, 2023
@riginoommen
Copy link

I want to install yarn 3 only

Wjhat should I do to make this happen from this step

    - npm i -g corepack && corepack enable && corepack prepare yarn@stable --activate
    - yarn -v

Can some one really help this. this kind of unstable process is troubling us a lot. our pipelines are broken

@arcanis
Copy link
Member

arcanis commented Oct 25, 2023

Can some one really help this. this kind of unstable process is troubling us a lot. our pipelines are broken.

I already answered you in the thread you opened (#5865).

And keep in mind for the future that stable is always the latest stable release (similarly, canary is always the latest release, stable or not). This is a fairly common pattern in software development. If you wish to always use a specific version, then explicitly state you want this specific version.

@riginoommen
Copy link

At least put documentation on the yarn 3 specific installation. thing is how an end user knows you are following this model. of the version bumps

@milesj
Copy link

milesj commented Oct 25, 2023

What's so difficult about yarn set version 3.6.3 or corepack prepare [email protected]?

Of course the "stable" tag is always going to point to the latest... stable. Which is v4.

@riginoommen
Copy link

It's not difficult but need to be documented

@appsforartists
Copy link
Author

You mean, like, right there?

I don't know why you're trying to take a thread about updating the docs to help users stay on the current version on your sidequest to pin your personal copy to some random version.

@riginoommen
Copy link

Exactly like this

@riginoommen
Copy link

When I search for yarn 3 installation it points to the stable tag

@appsforartists
Copy link
Author

Some days, GitHub needs a 🤦‍♂️ reaction…

@jdbertron
Copy link

You guys think we always have all the time in the world to untangle a mess cause by such a simple command.

@RDIL RDIL added the documentation This issue or pull request is about the documentation label Jun 13, 2024
@RDIL RDIL removed their assignment Jun 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation This issue or pull request is about the documentation
Projects
None yet
Development

No branches or pull requests

7 participants