chore(deps): update dependency npm-check-updates to v3.2.2#143
Open
renovate[bot] wants to merge 1 commit intomasterfrom
Open
chore(deps): update dependency npm-check-updates to v3.2.2#143renovate[bot] wants to merge 1 commit intomasterfrom
renovate[bot] wants to merge 1 commit intomasterfrom
Conversation
4bdd92a to
22d73c7
Compare
22d73c7 to
6edc0ca
Compare
6edc0ca to
3247205
Compare
3247205 to
57ca924
Compare
57ca924 to
9ced210
Compare
This file contains hidden or 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
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.
This PR contains the following updates:
3.1.20→3.2.2Release Notes
raineorshine/npm-check-updates (npm-check-updates)
v3.2.2Compare Source
ncu v3 excluded prerelease versions (
-alpha,-beta, etc) from the remote by default, as publishing prerelease versions tolatestis unconventional and not recommended. Prereleases versions can be included by specifying--pre(and is implied in options--greatestand--newest).However, when you are already specifying a prerelease version in your package.json dependencies, then clearly you want ncu to find newer prerelease versions. This is now default in v4, albeit with the conservative approach of sticking to the
latesttag.Migration
No effect for most users.
If a prerelease version is published on the
latesttag, and you specify a prerelease version in your package.json, ncu will now suggest upgrades for it.If a prerelease version is published on a different tag, there is no change from ncu v3; you will still need
--pre,--greatest, or--newestto get prerelease upgrades.raineorshine/npm-check-updates@v3.2.2...v4.0.0
v3.2.1Compare Source
v3.2.0Compare Source
Added
--engines-nodeoption to include only packages that satisfy engines.node as specified in the package file.See unit tests for detailed behavior.
v3.1.26Compare Source
v3.1.25Compare Source
v3.1.24Compare Source
v3.1.23Compare Source
v3.1.22Compare Source
v3.1.21Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.