-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
0.17.3 not found in debian repository #1900
Comments
I would follow along #1859. I don't think there will be a release out to the official installation methods (e.g. Debian repository) until the checklist is finished. |
Thanks for the quick reply, @wyze. Is there any general way to know when a new version has been officially shipped? Until now I just followed the GitHub Releases. |
Normally, once you see it on the GitHub releases, that is when it would be in all the official channels. It's just that there was a lot of breakage with 0.17.0, that they rolled back to 0.16.1 until we can fix the major regressions with 0.17.x. |
Hello @hpurmann! @wyze is correct - 0.17.0 had quite a few regressions so we had to roll back. A fixed 0.17 release should be coming out today, at which point we'll update the Debian repo. Normally the Debian repo is in sync with the GitHub releases. Thanks for your patience 😄 Alternatively, if you want to live on the edge, we have a 'nightly' Debian repo that contains the very latest code. I'd advise against doing that in production, but it's nice for testing. The source line for the testing repo is:
More info is available at https://yarnpkg.com/en/docs/nightly. |
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
It still installs 0.16.1
If the current behavior is a bug, please provide the steps to reproduce.
Run
apt-get update && apt-get install -y yarn
What is the expected behavior?
I want be able to upgrade manually by specifying the version of yarn in my
Dockerfile
:Please mention your node.js, yarn and operating system version.
Docker image extends from node 6.9.1
The text was updated successfully, but these errors were encountered: