upgrade-runtime-pins
Skill381 starsChanged 10 days agoISCView on GitHub
Upgrade the runtime version pins that live outside package.json dependency maps (Node, pnpm, bun) and open a PR
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- audit-convexSkill
- create-changesetSkill
- effectSkill
- managing-prereleasesSkill
- release-docsSkill
- upgrade-internal-depsSkill
- upgrade-published-depsSkill
- writing-commit-messagesSkill
- writing-technical-documentationSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
If nothing gets applied, say so and stop—no branch, no PR, even if a major-line jump was spotted and deferred.
- Very specific: line 35
Verify by reinstalling with the new versions and running the full repo checks (pnpm check, pnpm test, pnpm build).
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
enginesfloors 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 againstmain, noting in the body which pins moved and linking their release notes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

