@draekien/create-d9-app 0.0.4 → 0.0.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/package.json +1 -1
  2. package/templates/base/.agents/skills/upgrade-dependencies/SKILL.md +19 -10
  3. package/templates/base/.claude/skills/upgrade-dependencies/SKILL.md +19 -10
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@draekien/create-d9-app",
3
- "version": "0.0.4",
3
+ "version": "0.0.5",
4
4
  "type": "module",
5
5
  "description": "Scaffold a Turborepo monorepo with the draekien default stack",
6
6
  "license": "MIT",
package/templates/base/.agents/skills/upgrade-dependencies/SKILL.md CHANGED
@@ -1,15 +1,15 @@
1
1
  ---
2
2
  name: upgrade-dependencies
3
- description: Upgrades outdated patch and minor dependency pins in a pnpm, npm, yarn or bun workspace to exact versions, runs build, check, typecheck and test, and reports every change. Applies when asked to "upgrade dependencies", "update packages", "bump versions", or "update deps".
3
+ description: Upgrades outdated patch and minor dependency pins in a pnpm, npm, yarn or bun workspace to exact versions, holds major upgrades until the developer confirms each one, runs build, check, typecheck and test, and reports every change. Applies when asked to "upgrade dependencies", "update packages", "bump versions", "update deps", or "confirm major upgrades".
4
4
  argument-hint: "[--accept]"
5
5
  allowed-tools: Bash(npm view *), Bash(gh release view *), Bash(gh api *), Bash(pnpm *), Bash(npm *), Bash(yarn *), Bash(bun *), Bash(git diff *), Bash(git status *)
6
6
  ---
7
7
 
8
8
  # Upgrade dependencies
9
9
 
10
- Arguments: `$ARGUMENTS`. `--accept` means the developer accepts the breaking-change list in advance; proceed at step 4 without stopping.
10
+ Arguments: `$ARGUMENTS`. `--accept` means the developer accepts the patch and minor breaking-change list in advance; proceed at step 4 without stopping. `--accept` never confirms a major.
11
11
 
12
- Apply patch and minor upgrades only. Never apply a major; list it as `held: major`.
12
+ Apply patch and minor upgrades without per-package confirmation. Apply a major only after the developer confirms that package in step 7.
13
13
 
14
14
  ## 1. Read the workspace
15
15
 
@@ -45,10 +45,11 @@ A package with one version returns `versions` as a string, not an array.
45
45
  Candidates: versions without a `-` prerelease suffix, with `time[version]` at least the minimum age before now.
46
46
 
47
47
  - Same major as the pin, newer than the pin: take the highest. Type is `minor` if the minor differs, else `patch`.
48
- - Higher major exists: record `held: major` with the highest eligible version. Do not apply it.
48
+ - Higher major exists: record the highest eligible version as a pending major. Do not apply it before step 7.
49
49
  - No candidate newer than the pin: current.
50
+ - A 0.x pin is compared by its first non-zero segment: 0.13 to 0.14 is a major, 0.13.0 to 0.13.1 is a patch.
50
51
 
51
- If every pin is current, change no files, report `all pins current`, and stop.
52
+ A pin is current when it has no eligible patch or minor. If no pin has an eligible patch or minor, change no files and skip to step 7. If no major is pending either, report `all pins current` and stop.
52
53
 
53
54
  ## 3. Read release notes
54
55
 
@@ -64,7 +65,7 @@ gh release view v<version> --repo <owner>/<repo> --json body
64
65
 
65
66
  ## 4. Surface and stop
66
67
 
67
- Print one list: package, old version, new version, type, breaking changes and migrations (or `none found`). Then:
68
+ Print one list of patch and minor upgrades: package, old version, new version, type, breaking changes and migrations (or `none found`). Then:
68
69
 
69
70
  - Without `--accept`: stop and ask the developer to accept or exclude packages. Edit nothing before the answer.
70
71
  - With `--accept`: continue.
@@ -84,16 +85,24 @@ For each failure:
84
85
 
85
86
  Repeat until `build`, `check`, `typecheck` and `test` all exit 0. Never finish with a failing check.
86
87
 
87
- ## 7. Report
88
+ ## 7. Confirm and apply majors
88
89
 
89
- Print a table of changed packages:
90
+ After the patch and minor list, print each pending major as its own entry: package, current version, newest eligible major, and a summary of the release notes for the range current to new, read as in step 3, with breaking changes and migration steps called out.
91
+
92
+ - Ask the developer to confirm each major individually. Edit nothing before the answer. A major that is declined or not answered is held as `declined` or `not confirmed`.
93
+ - Apply confirmed majors one at a time: set the exact pin, run `<pm> install`, run the four scripts, and handle a failure as in step 6. A reverted major is `held: check failed`.
94
+
95
+ ## 8. Report
96
+
97
+ Print a table of changed packages, including applied majors:
90
98
 
91
99
  | Package | Old | New | Type |
92
100
  | --- | --- | --- | --- |
93
101
  | typescript | 5.9.2 | 5.9.3 | patch |
102
+ | vite | 7.1.0 | 8.0.0 | major |
94
103
 
95
104
  Below it list:
96
105
 
97
- - `held: major`: package, current version, newest eligible major.
98
- - `held: check failed`: package, old version, attempted version, error text.
106
+ - `held: major`: package, current version, newest eligible major, reason `declined` or `not confirmed`. List it even when every other pin is current; the no-change report is `all pins current` plus this list.
107
+ - `held: check failed`: package, old version, attempted version, error text. For a major, the reason is `check failed` with the error text.
99
108
  - Migrations applied, with the file changed.
package/templates/base/.claude/skills/upgrade-dependencies/SKILL.md CHANGED
@@ -1,15 +1,15 @@
1
1
  ---
2
2
  name: upgrade-dependencies
3
- description: Upgrades outdated patch and minor dependency pins in a pnpm, npm, yarn or bun workspace to exact versions, runs build, check, typecheck and test, and reports every change. Applies when asked to "upgrade dependencies", "update packages", "bump versions", or "update deps".
3
+ description: Upgrades outdated patch and minor dependency pins in a pnpm, npm, yarn or bun workspace to exact versions, holds major upgrades until the developer confirms each one, runs build, check, typecheck and test, and reports every change. Applies when asked to "upgrade dependencies", "update packages", "bump versions", "update deps", or "confirm major upgrades".
4
4
  argument-hint: "[--accept]"
5
5
  allowed-tools: Bash(npm view *), Bash(gh release view *), Bash(gh api *), Bash(pnpm *), Bash(npm *), Bash(yarn *), Bash(bun *), Bash(git diff *), Bash(git status *)
6
6
  ---
7
7
 
8
8
  # Upgrade dependencies
9
9
 
10
- Arguments: `$ARGUMENTS`. `--accept` means the developer accepts the breaking-change list in advance; proceed at step 4 without stopping.
10
+ Arguments: `$ARGUMENTS`. `--accept` means the developer accepts the patch and minor breaking-change list in advance; proceed at step 4 without stopping. `--accept` never confirms a major.
11
11
 
12
- Apply patch and minor upgrades only. Never apply a major; list it as `held: major`.
12
+ Apply patch and minor upgrades without per-package confirmation. Apply a major only after the developer confirms that package in step 7.
13
13
 
14
14
  ## 1. Read the workspace
15
15
 
@@ -45,10 +45,11 @@ A package with one version returns `versions` as a string, not an array.
45
45
  Candidates: versions without a `-` prerelease suffix, with `time[version]` at least the minimum age before now.
46
46
 
47
47
  - Same major as the pin, newer than the pin: take the highest. Type is `minor` if the minor differs, else `patch`.
48
- - Higher major exists: record `held: major` with the highest eligible version. Do not apply it.
48
+ - Higher major exists: record the highest eligible version as a pending major. Do not apply it before step 7.
49
49
  - No candidate newer than the pin: current.
50
+ - A 0.x pin is compared by its first non-zero segment: 0.13 to 0.14 is a major, 0.13.0 to 0.13.1 is a patch.
50
51
 
51
- If every pin is current, change no files, report `all pins current`, and stop.
52
+ A pin is current when it has no eligible patch or minor. If no pin has an eligible patch or minor, change no files and skip to step 7. If no major is pending either, report `all pins current` and stop.
52
53
 
53
54
  ## 3. Read release notes
54
55
 
@@ -64,7 +65,7 @@ gh release view v<version> --repo <owner>/<repo> --json body
64
65
 
65
66
  ## 4. Surface and stop
66
67
 
67
- Print one list: package, old version, new version, type, breaking changes and migrations (or `none found`). Then:
68
+ Print one list of patch and minor upgrades: package, old version, new version, type, breaking changes and migrations (or `none found`). Then:
68
69
 
69
70
  - Without `--accept`: stop and ask the developer to accept or exclude packages. Edit nothing before the answer.
70
71
  - With `--accept`: continue.
@@ -84,16 +85,24 @@ For each failure:
84
85
 
85
86
  Repeat until `build`, `check`, `typecheck` and `test` all exit 0. Never finish with a failing check.
86
87
 
87
- ## 7. Report
88
+ ## 7. Confirm and apply majors
88
89
 
89
- Print a table of changed packages:
90
+ After the patch and minor list, print each pending major as its own entry: package, current version, newest eligible major, and a summary of the release notes for the range current to new, read as in step 3, with breaking changes and migration steps called out.
91
+
92
+ - Ask the developer to confirm each major individually. Edit nothing before the answer. A major that is declined or not answered is held as `declined` or `not confirmed`.
93
+ - Apply confirmed majors one at a time: set the exact pin, run `<pm> install`, run the four scripts, and handle a failure as in step 6. A reverted major is `held: check failed`.
94
+
95
+ ## 8. Report
96
+
97
+ Print a table of changed packages, including applied majors:
90
98
 
91
99
  | Package | Old | New | Type |
92
100
  | --- | --- | --- | --- |
93
101
  | typescript | 5.9.2 | 5.9.3 | patch |
102
+ | vite | 7.1.0 | 8.0.0 | major |
94
103
 
95
104
  Below it list:
96
105
 
97
- - `held: major`: package, current version, newest eligible major.
98
- - `held: check failed`: package, old version, attempted version, error text.
106
+ - `held: major`: package, current version, newest eligible major, reason `declined` or `not confirmed`. List it even when every other pin is current; the no-change report is `all pins current` plus this list.
107
+ - `held: check failed`: package, old version, attempted version, error text. For a major, the reason is `check failed` with the error text.
99
108
  - Migrations applied, with the file changed.