@nocobase/app-skills 0.1.0-beta.31 → 0.1.0-beta.32

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.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nocobase/app-skills",
3
- "version": "0.1.0-beta.31",
3
+ "version": "0.1.0-beta.32",
4
4
  "description": "Agent Skills for developing, upgrading and deploying NocoBase applications.",
5
5
  "license": "Apache-2.0",
6
6
  "repository": {
@@ -47,13 +47,27 @@ node -p "JSON.stringify(require('./package.json').nocobase, null, 2)"
47
47
 
48
48
  If `nocobase.templatePackage` is missing, use the confirmed package name for `TEMPLATE` instead of the manifest lookup below, then record it in the manifest during the agreed source merge.
49
49
 
50
- ## 3. Fetch both releases
50
+ ## 3. Select the release channel and fetch both releases
51
+
52
+ Resolve the user's requested channel before choosing TARGET. An explicit version takes precedence. For a beta upgrade, use the template's `beta` dist-tag; for an explicit `latest` upgrade, use its `latest` dist-tag. If the user only asks to upgrade, retain the baseline's channel: use `beta` for a beta baseline and `latest` for a stable baseline; clarify other prerelease channels instead of guessing. State the selected channel and resolved version in the upgrade plan.
53
+
54
+ The tags are independent pointers, not a version ordering: `beta` tracks beta releases, while `latest` is npm's default tag and can still point to an older beta before a stable release exists. Do not assume `latest` is newer or stable, or choose the highest version across all channels. If the user asks for a stable release but `latest` resolves to a prerelease, explain that the tag does not provide a stable target and clarify before proceeding. A missing requested tag is not permission to fall back to another channel.
51
55
 
52
56
  ```bash
53
57
  REGISTRY=https://registry.npmjs.org
54
58
  TEMPLATE=$(node -p "require('./package.json').nocobase.templatePackage")
55
59
  BASE=$(node -p "require('./package.json').nocobase.defaultTemplateVersion")
56
- TARGET=<target version>
60
+ npm view "$TEMPLATE" dist-tags --json --registry="$REGISTRY"
61
+
62
+ # Set CHANNEL to beta or latest according to the selection above.
63
+ CHANNEL=beta
64
+ TARGET=$(npm view "$TEMPLATE@$CHANNEL" version --registry="$REGISTRY")
65
+ # For an explicitly requested version, assign that exact version to TARGET instead.
66
+ ```
67
+
68
+ Use semantic version ordering to compare the resolved TARGET with BASE. If equal, there is no template upgrade; if older, report the result rather than performing an implicit downgrade. Resolve a tag once, then use that exact version for fetching, the source diff and `defaultTemplateVersion`, even if the tag moves during the upgrade. Fetch dependencies from the target template's manifest; do not independently move every `@nocobase/*` dependency to a dist-tag, since packages have separate versions and release schedules.
69
+
70
+ ```bash
57
71
  WORK=$(mktemp -d)
58
72
 
59
73
  for VERSION in "$BASE" "$TARGET"; do
@@ -65,8 +79,6 @@ done
65
79
 
66
80
  These are published tarballs, not Git checkouts — they carry only what `files` publishes, and npm never publishes `.gitignore`. That is fine: both sides are missing the same things.
67
81
 
68
- Do not read the `beta` dist-tag as "newest". While every release is a prerelease, changesets tags each one `latest` and leaves `beta` on the first version ever published.
69
-
70
82
  ## 4. Read what changed, and who else changed it
71
83
 
72
84
  ```bash