stack-upgrade
Use when a Renovate pull request bumps @moifort/stack in a project, to sync the rules and apply the version's migrations.
SKILL.mdskills/stack-upgrade/SKILL.md
GitHubUpgrade the stack in a project
- Confirm the pull request bumps
@moifort/stack. Otherwise this skill does not apply. - In the pull request's branch:
bun install,bunx stack sync, commitchore(stack): sync to <version>. - Read the Upgrade part of every
CHANGELOG.mdsection between the two versions (node_modules/@moifort/stack/CHANGELOG.md), thenbunx stack migrations <old> <new> --json: the migrations between the two versions, for this project's stacks, in order. - For each migration, in order:
- read the rule it points to and its body (what changes, how to find it, how to fix it, when it does not apply);
- find the affected code, fix it, run its
checkcommand until it exits 0; - commit
refactor(<scope>): <migration id>; - when it does not apply, note why and commit nothing.
bun run preflight(andbun run ios:buildwith the ios stack). A failure caused by a migration: revert that migration's commit and mark itneeds review.- If the version changed a routine (
stack/routines/), update the scheduled task. - Comment on the pull request: one line per migration, its outcome (applied, not applicable, needs review) and the files touched.
- Merge only when every migration is
safe, each applied or not applicable, everycheckpasses and CI is green. Otherwise labelstack:reviewand leave it open.
Never edit stack/ by hand, never edit a rule from a project: a wrong rule is reported.