-
Notifications
You must be signed in to change notification settings - Fork 30k
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
meta: npm v4 tracking issue #8977
Comments
Do you know if there's a changelog or roadmap for npm v4? I haven't seen anything in their repo. |
@Daniel15 I believe the |
I think they gave up on that schedule. From the link @kenany posted:
|
EDIT: (beta) |
It seems that they had some divine power and npm@4.0.0 going to be released very soon. There is only one issue in milestone to update documentation. |
@nodejs/ctc ... Given that v7.0.0 will be released in 3 days and we still do not have a PR that we can use to test npmv4 in core, I'm going to pull this off the v7.0.0 milestone. Hopefully we'll be able to do the bump up to v4 as semver-minor in a v7.x soonish... |
To get feedbacks from users, this is still important since npm@3 will be under LTS and npm@4 will be the active latest version. Like @jasnell said, I also hope we'll be able to bump the version of npm to v4 as semver-minor update in Node v7 |
Dropping a note that a lot of relevant discussion is happening over at #9284 for future readers <3 |
@nodejs/ctc: npm inc is currently working on npm v4. The beta is expected to land on Oct 21st, stable on Oct 27th, two days after our scheduled ship date for v7. We likely won't get a PR for it until the 21st. Given that it's a semver-major update, we need to decide how to handle the update relative to the v7.0.0 release.
/cc @nodejs/npm @zkat @iarna
The text was updated successfully, but these errors were encountered: