chore(deps): update dependency release-it to v21 - #63
Conversation
Userscript Version PreviewPreview only — versions and CHANGELOGs are bumped automatically on merge to
|
44e2b6e to
2531089
Compare
There was a problem hiding this comment.
🟢 Approve — release-it v20 → v21
Renovate major bump of one dev dep. Two files: package.json and the corresponding yarn.lock churn. No source changes. PR was already automerged.
The v21 release notes call out three things that could reasonably bite a downstream: a Node ≥22.21 floor, a rewrite to strict CLI arg parsing (release-it/release-it#1196), and a refresh of the proxy-agent chain. I walked each against how this repo actually uses release-it and none of them apply.
Verification
Node floor — safe. package.json engines is >=24.18.0; .nvmrc = 24.18.0; mise.toml pins node = "24.19.0". All comfortably above the new 22.21 minimum.
CLI usage — safe. scripts/auto-bump-packages.sh invokes release-it in exactly one place:
if ! ( cd "$pkg_dir" && "$RELEASE_IT" --ci >&2 ); thenJust --ci, a first-class flag. Strict arg parsing has nothing to reject.
Config surface — safe. .release-it.base.json uses only git.{commit,tag,push,requireCleanWorkingDir,requireUpstream,getLatestTagFromAllRefs}, npm.publish, github.release, increment. Per-package .release-it.js files add the @release-it/conventional-changelog plugin (already at ^12.0.0, which is the v21-compatible line). None of these keys were removed or renamed in v21.
Publish path — safe. npm.publish: false and github.release: false mean the v21 fixes to npm workspace resolution (release-it/release-it#1312) and GitHub proxy routing don't touch this repo. Release publishing here is done directly by .github/workflows/release.yaml via gh release create, not by release-it.
Lockfile — consistent. The transitive churn is exactly what release-it 21.0.2 pulls in:
@inquirer/core11 → 12 (and every@inquirer/*prompt bumped in lockstep)- proxy-agent chain:
agent-base8→9,http/https-proxy-agent8→9,socks-proxy-agent9→10,pac-{proxy,resolver}-agent8→9,proxy-agent7→8, plus newproxy-agent-negotiate@1.1.0(kerberos is peer-optional, so no forced install) undici7.28 → 7.29,ora9.3 → 9.4,eta4.5 → 4.6,semver7.7.4 → 7.8.5,tinyglobby0.2.15 → 0.2.17giget2 → 3 (which is whycitty,consola,node-fetch-native,nypm,tinyexeccorrectly drop out — v3 bundles its CLI deps)yargs-parsercorrectly removed (v21 dropped the direct dep)
No stray additions, no version splits, and the existing resolutions.yoctocolors pin is untouched.
Not flagged as issues, for completeness
@release-it/conventional-changelog@^12.0.0was already on the v21-compatible major before this PR, so no companion bump is needed.- Renovate
automergeis on, gated by CI (.github/workflows/ci.ymlbuilds + tests every package). Given the analysis above, that's the right gate for a change this scoped.
Recommendation: approve. No follow-ups.
This PR contains the following updates:
^20.2.1→^21.0.0Release Notes
release-it/release-it (release-it)
v21.0.0Compare Source
1e90d9f) - thanks @trueberryless!38355d8)3bf251f) - thanks @cyphercodes!e4e9d0e) - thanks @microHoffman!56c70c3)0332c4a)caf77c9)8d1f752) - thanks @Mopsgamer!e7e04ef)1ed9cdd)c055e7f)98c45c4)70ab576)5c55139)daab846)52c89a7)ba4326f)df94838)c381a2d)2637e8a)Configuration
📅 Schedule: (in timezone America/New_York)
🚦 Automerge: Enabled.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.