Skip to content

Bump npm-check-updates from 21.0.3 to 22.1.0#21

Merged
loki980 merged 1 commit into
developfrom
dependabot/npm_and_yarn/develop/npm-check-updates-22.1.0
May 5, 2026
Merged

Bump npm-check-updates from 21.0.3 to 22.1.0#21
loki980 merged 1 commit into
developfrom
dependabot/npm_and_yarn/develop/npm-check-updates-22.1.0

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 2, 2026

Bumps npm-check-updates from 21.0.3 to 22.1.0.

Release notes

Sourced from npm-check-updates's releases.

v22.1.0

What's Changed

Full Changelog: raineorshine/npm-check-updates@v22.0.1...v22.1.0

v22.0.1

What's Changed

Full Changelog: raineorshine/npm-check-updates@v22.0.0...v22.0.1

v22.0.0

Breaking Changes

--cooldown now falls back to the greatest non-prerelease version rather than skipping the upgrade entirely when the latest version falls within the cooldown window.

  • This only affects --cooldown (or inferred cooldown from min-release-age/minimumReleaseAge/npmMinimalAgeGate).
  • This only affects --target latest (which is the default).

⚠️ WARNING

In rare circumstances, it is now possible for ncu --cooldown 10 to install a version that was never published to latest. This is because the npm registry does not store a history of versions published to the latest dist-tag. It is impossible to fall back to an earlier latest version, because there is no record of it. However, we do have a list of all published versions, and it's likely that a boring version like 1.0.1 was published to latest at some point. Versions like 1.0.1-pre.0, 1.0.1-beta, 1.0.1-build.58157394, etc will be ignored, as you would expect.

While npm-check-updates typically takes a conservative approach to version upgrades, following semver exactly and only upgrading to the latest version, falling back to the highest version outside the cooldown window is clearly the more intuitive behavior, and this outweighs the few cases where the results would be undesirable. The discussion in #1556 and the large amount of confusion since the initial release of --cooldown attest to this.

How to opt out of the new behavior

You can opt out of the new behavior by using --target "@latest". This forces a strict upgrade (or downgrade) to the latest tag only, without any fallback behavior.

For granular control, use a custom ncurc function to set the target or disable cooldown for a single package.

What's Changed

New Contributors

... (truncated)

Commits
  • 55ee69b 22.1.0
  • 43484c5 fix: ignore .pnpm-store in glob traversal to prevent OOM with --deep (#1705)
  • 7cd7687 Enhance --format time: consistent caching, interactive support, and human-r...
  • 191a2ce Bump vite-bundle-analyzer from 1.3.7 to 1.3.8 (#1700)
  • 3adb697 Bump @​types/bun from 1.3.12 to 1.3.13 (#1699)
  • 403f966 Bump eslint-plugin-promise from 7.2.1 to 7.3.0 (#1702)
  • eaa870c Bump @​typescript-eslint/eslint-plugin from 8.59.0 to 8.59.1 (#1697)
  • e84834a fix: make --dep and --format robust to PowerShell arg rewriting (comma-or-spa...
  • 28b5fcb 22.0.1
  • 127c552 fix: suppress cooldown config log messages when JSON output is active (#1692)
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels May 2, 2026
@loki980
Copy link
Copy Markdown
Owner

loki980 commented May 5, 2026

@dependabot rebase

Bumps [npm-check-updates](https://github.com/raineorshine/npm-check-updates) from 21.0.3 to 22.1.0.
- [Release notes](https://github.com/raineorshine/npm-check-updates/releases)
- [Changelog](https://github.com/raineorshine/npm-check-updates/blob/main/CHANGELOG.md)
- [Commits](raineorshine/npm-check-updates@v21.0.3...v22.1.0)

---
updated-dependencies:
- dependency-name: npm-check-updates
  dependency-version: 22.1.0
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/develop/npm-check-updates-22.1.0 branch from 9a60be8 to 6a6b076 Compare May 5, 2026 05:38
@loki980 loki980 merged commit df34997 into develop May 5, 2026
4 checks passed
@loki980 loki980 deleted the dependabot/npm_and_yarn/develop/npm-check-updates-22.1.0 branch May 5, 2026 05:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant