upgrade-prerelease-deps
Skill2 starsChanged 23 days agoMITView on GitHub
Upgrade dependencies in this repo, above all the pinned pre-release ones (nitro, @tanstack/react-start, oxfmt, @hey-api/openapi-ts). Use when bumping any package version, reviewing a Renovate PR, acting on pnpm audit:check, or when an install fails the release quarantine.
- Installs packages
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- tests/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- tests/CLAUDE.mdCLAUDE.md
- add-featureSkill
- add-pageSkill
- api-changeSkill
- auth-changeSkill
- database-changeSkill
- shadcnSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 43
Run pnpm check, pnpm check:drift, and pnpm build && pnpm verify:app.
≈ “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 dependencies
Policy
package.jsonuses exact versions (savePrefix: '';tests/unit/repo-policy.test.tschecks), andpnpm-lock.yamlis committed with them. pnpm 12 blocks dependency build scripts (allowBuilds) and quarantines fresh releases (minimumReleaseAge, one day, strict: a younger version fails the install instead of being excluded silently). Each exception names an exact version and its reason inpnpm-workspace.yaml.trustPolicy: no-downgradefails a version published with weaker provenance than an earlier one, andstrictPeerDependenciesan unmet peer. Every frozen install checks the lockfile against these policies.- A vulnerable transitive package gets an exact
overridesentry inpnpm-workspace.yamlnaming the advisory (and anignoreDependencyOverridesentry in.fallowrc.json, since the overridden version is no longer in the lockfile). An advisory that cannot apply here goes inauditConfig.ignoreGhsasinpnpm-workspace.yaml, with a comment giving the reason and a review date (write it by hand;pnpm audit --ignoreadds the id without the comment).pnpm audit:checkis the gate; Renovate's OSV alerts open fix PRs. - Pre-release packages, pinned exactly:
nitro(its npmlatestis a-betabuild),@tanstack/react-start(npmlatestis a 1.x release, but Start's docs still call it a Release Candidate),oxfmt(0.x, announced as beta) and@hey-api/openapi-ts(anextsnapshot, below). - Skills are pinned to a commit (
skills-lock.json); update the shadcn skill in the PR that bumpsshadcn(docs/agents/skills.md). Docs shipped inside packages are pinned by the lockfile.
Steps
- Renovate (
.github/renovate.json) opens the PRs, a week after each release; it follows thenextdist-tag for Hey API. By hand,pnpm outdatedlists what is newer. - Upgrade one pre-release package per PR:
pnpm add --save-exact <name>@<version>. - Package-specific work:
- Effect (stable since 4.0.0): upgrade
@effect/vitestwith it, runpnpm codegen, and review theopenapi.jsondiff. A check the document lost is a reason to stop: 4.0.0 exports aSchema.isPatternonly when its RegExp has theuflag. - Hey API: stays on the
nextsnapshot0.0.0-next-20260930190945. The stable 0.99.0 needs the JS compiler API that TypeScript 7 no longer has, and crashes; Renovate followsnextonly (ADR 0002). After any bump, runpnpm codegenand review thesrc/sdkdiff. - @effect/tsgo (0.x): the tsconfig plugin serves editors and
effect-tsgo diagnosticsis theeffectgate. Use it through those two only;effect-tsgo patchstays unused.
- Effect (stable since 4.0.0): upgrade
- Run
pnpm check,pnpm check:drift, andpnpm build && pnpm verify:app. All three must pass.
Done when
The three commands pass, package.json and pnpm-lock.yaml change together, and every exception added to
pnpm-workspace.yaml names the exact version and its reason.
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.

