chore(deps): update dependency npm-check-updates to v13 - autoclosed by renovate[bot] · Pull Request #28 · nos/core-plugin-staking-crypto

renovate · 2022-05-15T21:21:42Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
npm-check-updates	`^3.1.0` -> `^13.0.0`

Release Notes

raineorshine/npm-check-updates

`v13.0.0`

Compare Source

Breaking

node >= 14 is now required
Several options which have long been deprecated have been removed:
- --greatest - Instead use --target greatest
- --newest - Instead use --target newest
- --ownerChanged - Instead use --format ownerChanged
- --semverLevel - Renamed to --target

raineorshine/npm-check-updates@v12.5.12...v13.0.0

Added --retry <n> option to automatically retried failed requests for package information. Defaults to 3 retries.

Hopefully this relieves the frustrating situation of having npm-check-updates fail at the end of a long upgrade! You can control the number of retries with --retry <n>, including setting it to 0 for no retries (the previous behavior).

`v12.1.0`

Compare Source

`v12.0.5`

Compare Source

`v12.0.3`

Compare Source

`v12.0.2`

Compare Source

`v12.0.1`

Compare Source

`v12.0.0`

Compare Source

`v11.8.5`

Compare Source

`v11.8.4`

Compare Source

`v11.8.3`

Compare Source

`v11.8.2`

Compare Source

`v11.8.1`

Compare Source

`v11.8.0`

Compare Source

`v11.7.1`

Compare Source

`v11.7.0`

Compare Source

`v11.6.0`

Compare Source

`v11.5.13`

Compare Source

`v11.5.12`

Compare Source

`v11.5.11`

Compare Source

`v11.5.10`

Compare Source

`v11.5.9`

Compare Source

`v11.5.8`

Compare Source

`v11.5.7`

Compare Source

`v11.5.6`

Compare Source

`v11.5.5`

Compare Source

`v11.5.4`

Compare Source

`v11.5.3`

Compare Source

`v11.5.2`

Compare Source

`v11.5.1`

Compare Source

`v11.5.0`

Compare Source

Minor

npm-check-updates will now auto-detect yarn and apply --packageManager yarn when yarn.lock is present and package-lock.json is not present. You can override this by explicitly setting --packageManager npm. It will print "Using yarn" when the auto-detection is triggered.

`v11.4.1`

Compare Source

`v11.4.0`

Compare Source

Minor

Use --peer to check peer dependencies of installed packages and filter updates to compatible versions.
- 791aa22 Respect peer dependencies (#869)
Bump mem (minor)

Patch

696168b --deep: Fix Windows path
Bump dependencies (patch)

`v11.3.0`

Compare Source

`v11.2.3`

Compare Source

`v11.2.2`

Compare Source

`v11.2.1`

Compare Source

`v11.2.0`

Compare Source

Wildcards and globs can now be used in filters without having to use regex:

ncu react-*      # upgrade packages that start with "react-"
ncu \!commander  # upgrade everything except "commander"

Since special characters are not allowed in package names, this change shouldn't break anything, but please let me know if a filter that was working before v11.2.0 is not now!

Commits

ee27448 Add filter support for wildcards and glob expressions. Fixes #219.

`v11.1.11`

Compare Source

`v11.1.10`

Compare Source

`v11.1.9`

Compare Source

`v11.1.8`

Compare Source

`v11.1.7`

Compare Source

`v11.1.6`

Compare Source

`v11.1.5`

Compare Source

`v11.1.4`

Compare Source

`v11.1.3`

Compare Source

`v11.1.2`

Compare Source

`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

Specifiying both the --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

Versions marked as 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. a2111f4c2
Programmatic usage: run now defaults to silent: true instead of loglevel: 'silent, unless loglevel is explicitly specified. If you overrode silent or loglevel, this may affect the logging behavior. 423e024

Deprecated

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:

Runs npm install and npm test to ensure tests are currently passing.
Runs ncu -u to optimistically upgrade all dependencies.
If tests pass, hurray!
If tests fail, restores package file and lock file.
For each dependency, install upgrade and run tests.
When the breaking upgrade is found, saves partially upgraded package.json (not including the breaking upgrade) and exits.

Example:

$ ncu --doctor -u
npm install
npm run test
ncu -u
npm install
npm run test
Failing tests found:
/projects/myproject/test.js:13
  throw new Error('Test failed!')
  ^
Now let’s identify the culprit, shall we?
Restoring package.json
Restoring package-lock.json
npm install
npm install --no-save react@16.0.0
npm run test
  ✓ react 15.0.0 → 16.0.0
npm install --no-save react-redux@7.0.0
npm run test
  ✗ react-redux 6.0.0 → 7.0.0
Saving partially upgraded package.json

Github URLs

Added support for GitHub URLs.

See: f0aa792a4

Example:

{
  "dependencies": {
    "chalk": "https://github.com/chalk/chalk#v2.0.0"
  }
}

npm aliases

Added support for npm aliases.

See: 0f6f35c

Example:

{
  "dependencies": {
    "request": "npm:postman-request@2.88.1-postman.16"
  }
}

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: *owner changed*
Owner has not changed: no output
Owner information not available: *unknown*

Example:

$ ncu --ownerChanged
Checking /tmp/package.json
[====================] 1/1 100%

 mocha  ^7.1.0  →  ^8.1.3  *owner changed*

Run ncu -u to upgrade package.json

Commits

raineorshine/npm-check-updates@v7.1.1...v8.0.0

`v7.1.1`

Compare Source

`v7.1.0`

Compare Source

`v7.0.4`

Compare Source

`v7.0.3`

Compare Source

`v7.0.2`

Compare Source

`v7.0.1`

Compare Source

`v7.0.0`

Compare Source

Breaking

Removed bower support (4e4b47f)

Patch

Fix use of "<" with single digit versions (f04d00e)

Other

Change eslint configuration
Update dependencies
Replace cint methods with native methods
Add CI via GitHub Actions workflow

raineorshine/npm-check-updates@v6.0.2...v7.0.0

`v6.0.1`

Compare Source

`v6.0.0`

Compare Source

Breaking

--semverLevel now supports version ranges. This is a breaking change since version ranges are no longer ignored by --semverLevel, which may result in some dependencies having new suggested updates.

If you are not using --semverLevel, NO CHANGE! 😅

raineorshine/npm-check-updates@v5.0.0...v6.0.0

`v5.0.0`

Compare Source

Breaking

~node >= 8~
node >= 10.17

Bump minimum node version to v10.17.0 due to move-file #651

If ncu was working for you on v4.x, then v5.0.0 will still work. Just doing a major version bump since ncu's officially supported node version is changing. v4 should be patched to be compatible with node v8, but I'll hold off unless someone requests it.

raineorshine/npm-check-updates@v4.1.2...v5.0.0

`v4.1.2`

Compare Source

`v4.1.1`

Compare Source

`v4.1.0`

Compare Source

Feature

Added --concurrency to set the maximum number of concurrent HTTP requests to the npm registry (default: 8).

Fix

Pass --timeout correctly to pacote so that process is properly terminated when timeout is exceeded.

`v4.0.6`

Compare Source

`v4.0.5`

Compare Source

`v4.0.4`

Compare Source

`v4.0.3`

Compare Source

`v4.0.2`

Compare Source

`v4.0.1`

Compare Source

`v4.0.0`

Compare Source

ncu v3 excluded prerelease versions (-alpha, -beta, etc) from the remote by default, as publishing prerelease versions to latest is unconventional and not recommended. Prereleases versions can be included by specifying --pre (and is implied in options --greatest and --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 latest tag.

Migration

No effect for most users.

If a prerelease version is published on the latest tag, 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 --newest to get prerelease upgrades.

raineorshine/npm-check-updates@v3.2.2...v4.0.0

See unit tests for detailed behavior.

Configuration

📅 Schedule: At any time (no schedule defined).

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

If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

chore(deps): update dependency npm-check-updates to v13

6eb5f84

renovate Bot changed the title ~~chore(deps): update dependency npm-check-updates to v13~~ chore(deps): update dependency npm-check-updates to v13 - autoclosed Jun 18, 2022

renovate Bot closed this Jun 18, 2022

renovate Bot deleted the renovate/npm-check-updates-13.x branch June 18, 2022 18:53

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update dependency npm-check-updates to v13 - autoclosed#28

chore(deps): update dependency npm-check-updates to v13 - autoclosed#28
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/npm-check-updates-13.x

renovate Bot commented May 15, 2022

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

renovate Bot commented May 15, 2022

Release Notes

Breaking

Minor

Minor

Patch

Commits

Breaking

Features

Breaking

Breaking

Breaking

Deprecated

Features

Doctor Mode

Github URLs

npm aliases

Owner Changed

Commits

Breaking

Patch

Other

Breaking

Breaking

Feature

Fix