chore(deps): update dependency npm-check-updates to v11 - abandoned #1652
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:
7.1.1
->11.1.1
Release Notes
raineorshine/npm-check-updates
v11.1.1
Compare Source
v11.1.0
Compare Source
v11.0.2
Compare Source
v11.0.1
Compare Source
v11.0.0
Compare Source
Breaking
--packageFile
- Now interprets its argument as a glob pattern. It is possible that a previously supplied argument may be interepreted differently now (though I'm not aware of specific instances). Due to our conservative release policy we are releasing as a major version upgrade and allowing developers to assess for themselves.Features
--deep
- Run recursively in current working directory. Alias of--packageFile '**/package.json'
.See: #785
raineorshine/npm-check-updates@v10.3.1...v11.0.0
v10.3.1
Compare Source
v10.3.0
Compare Source
v10.2.5
Compare Source
v10.2.4
Compare Source
v10.2.3
Compare Source
v10.2.2
Compare Source
v10.2.1
Compare Source
v10.2.0
Compare Source
v10.1.1
Compare Source
v10.1.0
Compare Source
v10.0.0
Compare Source
Breaking
--filter
option and argument filters will now throw an error. Use one or the other. Previously the arguments would override the--filter
option, which made for a confusing result when accidentally not quoting the option in the shell. This change is only breaking for those who are relying on the incorrect behavior of argument filters overriding--filter
.See: #759
raineorshine/npm-check-updates@v9.2.4...v10.0.0
v9.2.4
Compare Source
v9.2.3
Compare Source
v9.2.2
Compare Source
v9.2.1
Compare Source
v9.2.0
Compare Source
v9.1.2
Compare Source
v9.1.1
Compare Source
v9.1.0
Compare Source
v9.0.4
Compare Source
v9.0.3
Compare Source
v9.0.2
Compare Source
v9.0.1
Compare Source
v9.0.0
Compare Source
Breaking
deprecated
in npm are now ignored by default. If the latest version is deprecated, the next highest non-deprecated version will be suggested. Use--deprecated
to include deprecated versions (old behavior).raineorshine/npm-check-updates@v8.1.1...v9.0.0
v8.1.1
Compare Source
v8.1.0
Compare Source
v8.0.5
Compare Source
v8.0.4
Compare Source
v8.0.3
Compare Source
v8.0.2
Compare Source
v8.0.1
Compare Source
v8.0.0
Compare Source
Breaking
--semverLevel major
is now--target minor
.--semverLevel minor
is now--target patch
. This change was made to provide more intuitive semantics for--semverLevel
(now--target
). Most people assumed it meant the inclusive upper bound, so now it reflects that. a2111f4c2run
now defaults tosilent: true
instead ofloglevel: 'silent
, unlessloglevel
is explicitly specified. If you overrodesilent
orloglevel
, this may affect the logging behavior. 423e024Deprecated
Options that controlled the target version (upper bound) of upgrades have been consolidated under
--target
. The old options are aliased with a deprecation warning and will be removed in the next major version. No functionality has been removed.--greatest
: Renamed to--target greatest
--newest
: Renamed to--target newest
--semverLevel
: Renamed to--target
See: 7eca5bf3
Features
Doctor Mode
#722
Usage:
ncu --doctor [-u] [options]
Iteratively installs upgrades and runs tests to identify breaking upgrades. Add
-u
to execute (modifies your package file, lock file, and node_modules).To be more precise:
npm install
andnpm test
to ensure tests are currently passing.ncu -u
to optimistically upgrade all dependencies.Example:
Github URLs
Added support for GitHub URLs.
See: f0aa792a4
Example:
npm aliases
Added support for npm aliases.
See: 0f6f35c
Example:
Owner Changed
#621
Usage:
ncu --ownerChanged
Check if the npm user that published the package has changed between current and upgraded version.
Output values:
*owner changed*
*unknown*
Example:
Commits
raineorshine/npm-check-updates@v7.1.1...v8.0.0
Renovate configuration
📅 Schedule: "before 3am on Monday" (UTC).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.