-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Upgrade to yarn 0.24.4 #400
Conversation
Thanks, but I think Yarn should be upgraded together with new Node.js releases, as proposed in #393. Therefore 👎 |
In my opinion the node-gyp regression is serious and should not remain unpatched: we need to address it either by merging this or #346. |
Ok, this could be justified in order to get to a stable working state before becoming more conservative with updates. If the other @nodejs/docker members agree, let's merge this.
Merging this would be the better option. |
I tend to agree. We can be stricter about updating yarn after this lands. |
Second it. LGTM
… On 13 May 2017, at 01:35, Christopher Horrell ***@***.***> wrote:
I tend to agree. We can be stricter about updating yarn after this lands.
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Merged. Working on Docker Hub PR. |
Docker Hub PR: docker-library/official-images#2950 |
Should close #381 as well