Repository navigation
build: bump dev-dependencies-common to 11.0.0 (npm-check-updates 23) - #616
Merged
Merged
Conversation
The only change between common 10.0.1 and 11.0.0 is npm-check-updates 22.2.9 → 23.0.0 — the biome/tsconfig/vitest presets are byte-identical, so nothing about this repo's lint, build, or test behavior moves. common went major because ncu is one of its runtime `dependencies`, and v23 raises the Node floor to ^22.22.2 || ^24.15.0 || >=26.0.0, which propagates here on install. CI already runs Node 22.x (v22.23.1), which clears it. v23's other breaking changes don't reach us: .ncurc.cjs still loads under pure-ESM ncu via Node's require(esm) path, no config uses the filterVersion/rejectVersion predicate forms that were removed, and the new grouped --format default is cosmetic. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01X6DpUPA4ofQeXDyLbhPzdW
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.
Bumps
@versini/dev-dependencies-common10.0.1 → 11.0.0.What actually changed
The only difference between common 10.0.1 and 11.0.0 is
npm-check-updates22.2.9 → 23.0.0. The biome / tsconfig / vitest presets are byte-identical between the two releases, so nothing about this repo's lint, build, or test behavior moves.common went major because ncu is one of its runtime
dependencies(not a devDependency), so v23's Node floor —^22.22.2 || ^24.15.0 || >=26.0.0— propagates here on install. CI runs Node 22.x, which resolves to v22.23.1 and clears it.Why v23 isn't disruptive
Its four breaking changes were checked against this ecosystem's actual usage:
.ncurc.cjsopens withrequire("npm-check-updates")fordefineConfig; that still resolves via Node'srequire(esm)path, since the v23 entry has no top-level await.filterVersion/rejectVersionlost predicate-function support. No.ncurc.cjsin any repo uses either. The three function-valued options in use —filterResults,cooldown,target— have identical signatures in v22 and v23.--formatnow defaults to grouped output. Cosmetic; upgrades are grouped by major/minor/patch.--target semverrespects upper bounds. No config usestarget: 'semver'.Verification
pnpm lint,pnpm test(pluspnpm typecheckwhere the repo has one) all pass locally against the new pin, andncuresolves to 23.0.0.🤖 Generated with Claude Code
https://claude.ai/code/session_01X6DpUPA4ofQeXDyLbhPzdW