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

meta: npm v4 tracking issue #8977

Closed
jasnell opened this issue Oct 7, 2016 · 8 comments
Closed

meta: npm v4 tracking issue #8977

jasnell opened this issue Oct 7, 2016 · 8 comments
Assignees
Labels
discuss Issues opened for discussions and feedbacks. meta Issues and PRs related to the general management of the project. npm Issues and PRs related to the npm client dependency or the npm registry.

Comments

@jasnell
Copy link
Member

jasnell commented Oct 7, 2016

@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

@jasnell jasnell added meta Issues and PRs related to the general management of the project. npm Issues and PRs related to the npm client dependency or the npm registry. discuss Issues opened for discussions and feedbacks. labels Oct 7, 2016
@jasnell jasnell added this to the 7.0.0 milestone Oct 7, 2016
@jasnell jasnell self-assigned this Oct 7, 2016
@Daniel15
Copy link

Daniel15 commented Oct 9, 2016

Do you know if there's a changelog or roadmap for npm v4? I haven't seen anything in their repo.

@kenany
Copy link
Contributor

kenany commented Oct 10, 2016

@Daniel15 I believe the 4.x milestone covers the very least of what's to come.

@felipou
Copy link

felipou commented Oct 21, 2016

I think they gave up on that schedule. From the link @kenany posted:

We're targeting a mid-February release of npm@4.0.0

@kenany
Copy link
Contributor

kenany commented Oct 21, 2016

Released

EDIT: (beta)

@bricss
Copy link

bricss commented Oct 21, 2016

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.

@jasnell
Copy link
Member Author

jasnell commented Oct 22, 2016

@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...

@jasnell jasnell removed this from the 7.0.0 milestone Oct 22, 2016
@watilde
Copy link
Member

watilde commented Oct 25, 2016

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

@zkat zkat mentioned this issue Oct 25, 2016
4 tasks
@zkat
Copy link
Contributor

zkat commented Oct 26, 2016

Dropping a note that a lot of relevant discussion is happening over at #9284 for future readers <3

@targos targos closed this as completed Jan 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Issues opened for discussions and feedbacks. meta Issues and PRs related to the general management of the project. npm Issues and PRs related to the npm client dependency or the npm registry.
Projects
None yet
Development

No branches or pull requests

8 participants