| name | upgrade-runtime-pins |
| description | Upgrade the runtime version pins that live outside package.json dependency maps (Node, pnpm, bun) and open a PR |
Upgrade the repo's pinned runtime versions and open a PR for review. Never
merge it yourself.
Scope
Version pins that live outside package.json dependency maps: .node-version,
the packageManager field in the root package.json, and the tool versions in
mise.toml. Not every consumer reads these files — some CI setup actions under
.github/actions/ resolve Node or pnpm from other sources — so after updating
a pin, check where each version is actually resolved and call out any consumer
the bump doesn't reach in the PR description. Do not touch GitHub Actions
uses: versions or devcontainer config — Dependabot owns those.
Rules
- Bump within each tool's current major line. Take a major line (a new Node
LTS, a pnpm or bun major) only if the release notes show nothing that
affects this repo and the checks stay green; otherwise describe the
available jump in the PR description (or in your final report, if the run
ends up applying nothing and opens no PR).
- Never change
engines floors in the published packages — those are
published-surface policy and belong to a deliberate, changeset-recorded
decision, not this routine.
Delivering
- If nothing gets applied, say so and stop — no branch, no PR, even if a
major-line jump was spotted and deferred; the next scheduled run will
surface it again.
- Verify by reinstalling with the new versions and running the full repo
checks (
pnpm check, pnpm test, pnpm build). Anything the local
environment genuinely can't run, leave to the PR's CI — and get it green.
- Push a branch (
deps/<short-description>, unless this session was assigned
a branch) and open a PR against main, noting in the body which pins moved
and linking their release notes.
