deps: upgrade npm to 6.6.0 #25551
Closed
deps: upgrade npm to 6.6.0 #25551
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nodejs-github-bot
added
the
npm
|
I think something may have gone wrong in the upgrade... it only appears to have changes to documentation. |
|
Sorry about that! Looks like it was a typo on my part. I pushed the correct version to the PR branch. |
|
Just to make sure we have a consistent process: our docs say we should be sending you the release candidate once it's final but before our own release. Is that correct? For example, I'd be sending 6.6.0-next.1 which became 6.6.0. |
|
When this PR eventually lands we want to have the official release.
The intention of release candidate was to allow the PR to be opened before
release was promoted.
We can change text /process if it doesn't make sense in practice
…On Fri, Jan 18, 2019, 3:00 PM Audrey Eschright ***@***.***> wrote:
Just to make sure we have a consistent process: our docs say we should be
sending you the release candidate once it's final but before our own
release. Is that correct? For example, I'd be sending 6.6.0-next.1 which
became 6.6.0.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#25551 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAecV3nmDy9ypHpW_zb8TykMYTc6Rxuuks5vEifagaJpZM4aGx2o>
.
|
|
npm 6.7.0 released. |
|
@aeschright should this PR be updated to have npm 6.7.0 instead of 6.6.0? |
|
Thanks @aeschright. Superseded by #25804. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passesWhere this should land
Notable Changes
This is a pre-release of
npm@6.6.0. This release marks the end of a massive internal refactor to npm that means we finally got rid of the legacynpm-registry-clientin favor of the shiny, new,window.fetch-likenpm-registry-fetch. Check the PR if you'd like to see the details.02c837e01#106 Makenpm dist-tagsthe same asnpm dist-tag ls. (@isaacs)1065a7809#65 Add support forIBM i. (@dmabupt)f58b43ef2npm.community#3983 Report any errors above 400 as potentially not supporting audit. (@zkat)Changelog