chore(deps): update dependency npm-check-updates to v16 #34

renovate · 2022-11-20T18:01:55Z

This PR contains the following updates:

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

Release Notes

raineorshine/npm-check-updates (npm-check-updates)

Feature

Added experimental support for bun package manager.
Automatically used if bun.lockb is detected.
Assistance needed to test it out on different platforms.

$ ncu --packageManager bun
$ ncu -p bun

Thanks to @ImBIOS for the PR!

`v16.13.4`

Compare Source

`v16.13.3`

Compare Source

`v16.13.2`

Compare Source

`v16.13.1`

Compare Source

`v16.13.0`

Compare Source

Feature

Added --install option to control auto-install behavior.

Usage:

ncu --install [value]

Default: prompt

Control the auto-install behavior.

always	Runs your package manager's install command automatically after upgrading.
never	Does not install and does not prompt.
prompt	Shows a message after upgrading that recommends an install, but does not install. In interactive mode, prompts for install. (default)

`v16.12.3`

Compare Source

`v16.12.2`

Compare Source

`v16.12.1`

Compare Source

`v16.12.0`

Compare Source

`v16.11.2`

Compare Source

`v16.11.1`

Compare Source

`v16.11.0`

Compare Source

`v16.10.19`

Compare Source

`v16.10.18`

Compare Source

`v16.10.17`

Compare Source

`v16.10.16`

Compare Source

`v16.10.15`

Compare Source

`v16.10.14`

Compare Source

`v16.10.13`

Compare Source

`v16.10.12`

Compare Source

`v16.10.11`

Compare Source

`v16.10.10`

Compare Source

`v16.10.9`

Compare Source

`v16.10.8`

Compare Source

`v16.10.7`

Compare Source

`v16.10.6`

Compare Source

`v16.10.5`

Compare Source

`v16.10.4`

Compare Source

`v16.10.3`

Compare Source

`v16.10.2`

Compare Source

`v16.10.1`

Compare Source

`v16.10.0`

Compare Source

Feature

Added filterResults option to filter out upgrades based on a user provided function.

filterResults runs after new versions are fetched, in contrast to filter and filterVersion, which run before. This allows you to filter out upgrades with filterResults based on how the version has changed (e.g. a major version change).

Only available in .ncurc.js or when importing npm-check-updates as a module.

/** Filter out non-major version updates.
  @&#8203;param {string} packageName               The name of the dependency.
  @&#8203;param {string} currentVersion            Current version declaration (may be range).
  @&#8203;param {SemVer[]} currentVersionSemver    Current version declaration in semantic versioning format (may be range).
  @&#8203;param {string} upgradedVersion           Upgraded version.
  @&#8203;param {SemVer} upgradedVersionSemver     Upgraded version in semantic versioning format.
  @&#8203;returns {boolean}                        Return true if the upgrade should be kept, otherwise it will be ignored.
*/
filterResults: (packageName, {currentVersion, currentVersionSemver, upgradedVersion, upgradedVersionSemver}) => {
  const currentMajorVersion = currentVersionSemver?.[0]?.major
  const upgradedMajorVersion = upgradedVersionSemver?.major
  if (currentMajorVersion && upgradedMajorVersion) {
    return currentMajorVersion < upgradedMajorVersion
  }
  return true
}

For the SemVer type definition, see: https://git.coolaj86.com/coolaj86/semver-utils.js#semverutils-parse-semverstring

Thanks to mslowiak for this enhancement!

`v16.9.0`

Compare Source

`v16.8.2`

Compare Source

`v16.8.1`

Compare Source

`v16.8.0`

Compare Source

Feature

Added --format lines

$ ncu --format lines
@&#8203;ava/typescript@^4.0.0
ava@^5.2.0
eslint@^8.36.0
lerna@^6.5.1
typescript@^5.0.2

This is particularly useful for upgrading global modules:

npm install -g $(ncu -g --format lines)

Thanks to @vanodevium for the PR!

`v16.7.13`

Compare Source

`v16.7.12`

Compare Source

`v16.7.11`

Compare Source

`v16.7.10`

Compare Source

`v16.7.9`

Compare Source

`v16.7.8`

Compare Source

`v16.7.7`

Compare Source

`v16.7.6`

Compare Source

`v16.7.5`

Compare Source

`v16.7.4`

Compare Source

`v16.7.3`

Compare Source

`v16.7.2`

Compare Source

`v16.7.1`

Compare Source

`v16.7.0`

Compare Source

`v16.6.5`

Compare Source

`v16.6.4`

Compare Source

`v16.6.3`

Compare Source

`v16.6.2`

Compare Source

`v16.6.1`

Compare Source

`v16.6.0`

Compare Source

`v16.5.6`

Compare Source

`v16.5.5`

Compare Source

`v16.5.4`

Compare Source

`v16.5.3`

Compare Source

`v16.5.2`

Compare Source

`v16.5.1`

Compare Source

`v16.5.0`

Compare Source

`v16.4.3`

Compare Source

`v16.4.2`

Compare Source

`v16.4.1`

Compare Source

`v16.4.0`

Compare Source

Feature

Added --cacheClear option for—you guessed it—clearing the cache 🫥.

This brings the suite of cache-related options to:

--cache : Cache versions to the cache file.
--cacheClear : Clear the default cache, or the cache file specified by --cacheFile.
--cacheExpiration <min> : Cache expiration in minutes (default: 10).
--cacheFile <path> : Filepath for the cache file (default: "~/.ncu-cache.json").

Thanks to @ly3xqhl8g9 whose code is gratefully more lucid than his username.

`v16.3.25`

Compare Source

`v16.3.24`

Compare Source

`v16.3.23`

Compare Source

`v16.3.22`

Compare Source

`v16.3.21`

Compare Source

`v16.3.20`

Compare Source

`v16.3.19`

Compare Source

`v16.3.18`

Compare Source

`v16.3.17`

Compare Source

`v16.3.16`

Compare Source

`v16.3.15`

Compare Source

`v16.3.14`

Compare Source

`v16.3.13`

Compare Source

`v16.3.12`

Compare Source

`v16.3.11`

Compare Source

`v16.3.10`

Compare Source

`v16.3.9`

Compare Source

`v16.3.8`

Compare Source

`v16.3.7`

Compare Source

`v16.3.6`

Compare Source

`v16.3.5`

Compare Source

`v16.3.4`

Compare Source

`v16.3.3`

Compare Source

`v16.3.2`

Compare Source

`v16.3.1`

Compare Source

`v16.3.0`

Compare Source

Feature

Added workspace support! 🚢

Upgrade all workspaces:

ncu --workspaces
ncu -ws

Upgrade a single workspace:

ncu --workspace a
ncu -w a

Upgrade more than one workspace:

ncu --workspace a --workspace b
ncu -w a -w b

Upgrade all workspaces AND the root project:

ncu --workspaces --root

Upgrade a single workspace AND the root project:

ncu --workspace a --root

Notes

If workspaces or --workspace is run in --interactive mode, ncu will prompt to npm install once in the root project rather than separately in each workspace (#1182).
Running --deep will not trigger workspace support.

`v16.2.1`

Compare Source

`v16.2.0`

Compare Source

`v16.1.3`

Compare Source

`v16.1.2`

Compare Source

`v16.1.1`

Compare Source

`v16.1.0`

Compare Source

`v16.0.6`

Compare Source

`v16.0.5`

Compare Source

`v16.0.4`

Compare Source

`v16.0.3`

Compare Source

`v16.0.2`

Compare Source

`v16.0.1`

Compare Source

`v16.0.0`

Compare Source

Breaking

Automatic detection of package data on stdin has been removed. This feature was deprecated in v14.0.0. Add --stdin for old behavior.
Wild card filters now apply to scoped packages. Previously, ncu -f '*vite*' would not include @vitejs/plugin-react. Now, filters will match any part of the package name, including the scope. Use a more specific glob or regex expression for old behavior.

raineorshine/npm-check-updates@v15.3.4...v16.0.0

`v15.3.4`

Compare Source

`v15.3.3`

Compare Source

`v15.3.2`

Compare Source

`v15.3.1`

Compare Source

`v15.3.0`

Compare Source

`v15.2.6`

Compare Source

`v15.2.5`

Compare Source

`v15.2.4`

Compare Source

`v15.2.3`

Compare Source

`v15.2.2`

Compare Source

`v15.2.1`

Compare Source

`v15.2.0`

Compare Source

`v15.1.0`

Compare Source

`v15.0.5`

Compare Source

`v15.0.4`

Compare Source

`v15.0.3`

Compare Source

`v15.0.2`

Compare Source

`v15.0.1`

Compare Source

`v15.0.0`

Compare Source

Breaking

node >= 14.14 is now required (#1145)
- Needed to upgrade update-notifier with has a moderate severity vulnerability
yarn autodetect has been improved (#1148)
- This is a patch, though technically it is breaking. In the obscure case where --packageManager is not given, there is no package-lock.json in the current folder, and there is a yarn.lock in an ancestor directory, npm-check-updates will now use yarn.
- More practically, if you needed to specify --packageManager yarn explicitly before, you may not have to now

raineorshine/npm-check-updates@v14.1.1...v15.0.0

`v14.1.1`

Compare Source

`v14.1.0`

Compare Source

Features

Group

You can now group upgrades by risk level using --format group:

Interactive Mode

Interactive mode was completely rewritten for a better user experience.

Inspired by npm-check.

Combine with --format group for a truly luxe experience:

Static Registry

A new option --packageManager staticRegistry allows upgrades to be recommended from a static JSON file. This can be used to power custom versioning infrastructure that is completely independent from the npm registry.

Thanks to agrouse who did a fine job on the PR.

Example:

$ ncu --packageManager staticRegistry --registry ./my-registry.json

my-registry.json:

{
  "prettier": "2.7.0",
  "typescript": "4.7.0"
}

The latest versions of prettier and typescript are set in the registry file. When ncu is run, it will recommend upgrades from the static registry file without touching the npm registry:

$ ncu --packageManager staticRegistry --registry ./my-registry.json
Checking /Users/raine/projects/ncu-issues/14.1.0/package.json
[====================] 2/2 100%

 prettier    ^2.0.1  →  ^2.7.0
 typescript  ^3.4.0  →  ^4.7.0

Run ncu -u to upgrade package.json

`v14.0.2`

Compare Source

`v14.0.1`

Compare Source

`v14.0.0`

Compare Source

Breaking

Prerelease versions are now "upgraded" to versions with a different preid.

For example, if you have a dependency at 1.3.3-next.1 and the version fetched by ncu is 1.2.3-dev.2, ncu will suggest an "upgrade" to 1.2.3-dev.2. This is because prerelease versions with different preids are incomparable. Since they are incomparable, ncu now assumes the fetched version is desired.

Since this change affects only prereleases, there is no impact on default ncu usage that fetches the latest version. With --pre 1 or --target newest or --target greatest, this change could affect which version is suggested if versions with different preids are published. The change was made to support the new --target @[tag] feature.

If you have a use case where this change is not what is desired, please report an issue. The intention is for zero disruption to current usage.

Features

You can now upgrade to a specific tag, e.g. --target @next. Thanks to IMalyugin.

raineorshine/npm-check-updates@v13.1.5...v14.0.0

`v13.1.5`

Compare Source

`v13.1.4`

Compare Source

`v13.1.3`

Compare Source

`v13.1.2`

Compare Source

`v13.1.1`

Compare Source

`v13.1.0`

Compare Source

`v13.0.4`

Compare Source

`v13.0.3`

Compare Source

`v13.0.2`

Compare Source

`v13.0.1`

Compare Source

`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

`v12.5.12`

Compare Source

`v12.5.11`

Compare Source

`v12.5.10`

Compare Source

`v12.5.9`

Compare Source

`v12.5.8`

Compare Source

`v12.5.7`

Compare Source

`v12.5.6`

Compare Source

`v12.5.5`

Compare Source

`v12.5.4`

Compare Source

`v12.5.3`

Compare Source

`v12.5.2`

Compare Source

`v12.5.1`

Compare Source

`v12.5.0`

Compare Source

`v12.4.0`

Compare Source

`v12.3.1`

Compare Source

`v12.3.0`

Compare Source

`v12.2.1`

Compare Source

`v12.2.0`

Compare Source

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

Breaking

node >= 12 is required. Time to upgrade that old-ass server you never touch.
peerDependencies are now excluded by default. Peer dependencies should use the lowest possible version that works. The old behavior encouraged a bad practice of uprading peer dependencies. You can use --dep prod,dev,optional,peer for the old behavior (#951).
Dependencies with > will be converted to >=. The old behavior was causing upgrades to > [latest] which was impossible (#957).

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

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.1.1`](https://togithub.com/raineorshine/npm-check-updates/compare/v1

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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, check this box

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

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

6ec9ef8

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update dependency npm-check-updates to v16 #34

chore(deps): update dependency npm-check-updates to v16 #34

renovate bot commented Nov 20, 2022 •

edited

chore(deps): update dependency npm-check-updates to v16 #34

Are you sure you want to change the base?

chore(deps): update dependency npm-check-updates to v16 #34

Conversation

renovate bot commented Nov 20, 2022 • edited

Release Notes

Feature

Feature

Feature

Feature

Feature

Feature

Notes

Breaking

renovate bot commented Nov 20, 2022 •

edited