chore(deps): update dependency release-it to v21

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
release-it	^20.2.1 → ^21.0.0

---

Release Notes

release-it/release-it (release-it)

v21.0.0

Compare Source

• fix(ci): do not run integration on forks (#​1315) (1e90d9f) - thanks @​trueberryless!
• Pin GitHub Actions to immutable commits (#​1316) (38355d8)
• Fix npm publish workspace config resolution (#​1312) (3bf251f) - thanks @​cyphercodes!
• Add gitlab.repoId option (#​1224) (e4e9d0e) - thanks @​microHoffman!
• Exit successfully when no release version is available (56c70c3)
• Support numeric GitLab repository IDs (0332c4a)
• Parse CLI arguments strictly (resolve #​1196) (caf77c9)
• fix: shell caching and working tree detection (#​1317) (8d1f752) - thanks @​Mopsgamer!
• Remove dependabot workflow (e7e04ef)
• Fix configured GitHub proxy routing (1ed9cdd)
• Upgrade dependencies and require Node 22 (c055e7f)
• Fix npm custom registry argument handling (resolve #​1318) (98c45c4)
• Pin GitLab releases to the current commit (resolve #​1216) (70ab576)
• Refresh GitHub Actions and package preview runtime (5c55139)
• Document v21 runtime requirements (daab846)
• Simplify git-cliff recipe (resolve #​1195) (52c89a7)
• Make GitLab CA tests platform-independent (ba4326f)
• Raise Node 22 requirement to 22.21 (df94838)
• Verify GitLab server certificates by default (c381a2d)
• Update changelog for v21 (2637e8a)

---

Configuration

📅 Schedule: (in timezone America/New_York)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • "after 10am and before 4pm every weekday"

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

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[henry-nsheaps]

Review Summary

Renovate dependency-only bump: release-it ^20.2.1 → ^21.0.0, plus the corresponding yarn.lock churn (proxy-agent 7→8, inquirer core 11→12, related transitives). release-it is a devDependency invoked exclusively by .github/workflows/release.yaml as yarn release-it --ci, so the blast radius is confined to release automation and the local mise run toolchain.

Verdict: 🟢 APPROVE — merged already, all checks green, no code changes and no config changes needed to support the new major.

How I arrived at this

• Diff scope — 2 files, +271/-331; only package.json is a semantic change, the rest is deterministic lockfile updates from yarn install. No .release-it.json change required; the yarn release-it --ci invocation is unaffected by v21's stricter CLI parsing since no ambiguous positional args are used.
• Breaking changes surveyed (from release-it v21 notes):
  • Node 22.21+ required. mise.toml uses node = "lts"; Node 22 LTS is well past 22.21, and CI (Test, check, Release) is green on this SHA. See inline note below.
  • Strict CLI arg parsing. Only --ci is passed in release.yaml:41 — safe.
  • yargs-parser dropped as a direct dep (visible in lockfile) — internal to release-it, no consumer impact.
  • Other listed changes (GitLab, npm workspace, GH proxy routing) don't apply to this repo's usage.
• CI signal — All required checks passed on 81878683 (Test, check, dispatch review), and the PR was auto-merged by Renovate at 02:15 UTC. yarn install and yarn release-it resolution both succeeded in the pipeline.
• Existing config sanity check — .release-it.json uses the standard hooks.after:bump, git, github, npm: false, and @release-it/conventional-changelog plugin. All of these APIs are still supported in v21.

Strengths

• Devdep-only change; production bin/git-wt bash script is untouched.
• Renovate config (renovate.json) extends shared config for consistency across your projects — good.
• Release automation uses mise-action, which will keep Node in step with the LTS floor without manual pinning.

Follow-ups

• P2 (informational) — see inline note on package.json: release-it@21 bumped its minimum Node to 22.21. Current mise.toml (node = "lts") satisfies it, but worth remembering if you ever pin to a specific line.

No P0/P1 items.

_{🤖 Review by claude-opus-4-7 · Reviewed at merge SHA 81878683 · No prior reviews to reconcile.}

[henry-nsheaps]

🟢 ℹ️ P2 — Node runtime floor raised to 22.21

release-it@21 requires Node 22.21+ (up from Node 20 in v20.x). The release workflow resolves Node via mise with node = "lts" in mise.toml, which currently satisfies this (Node 22 LTS is past 22.21), so no action is needed today.

Worth being aware of for the next Node LTS transition — if you ever pin node to a specific line older than 22.21 for reproducibility, yarn release-it will fail at install/runtime. Not a change requested for this PR.