@lifeaitools/rdc-skills 0.26.1 → 0.26.3
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/.claude-plugin/plugin.json +1 -1
- package/RELEASE.md +10 -2
- package/commands/deploy.md +16 -0
- package/git-sha.json +1 -1
- package/package.json +1 -1
package/RELEASE.md
CHANGED
|
@@ -27,11 +27,16 @@ git checkout master
|
|
|
27
27
|
git pull --ff-only origin master
|
|
28
28
|
git merge <feature-branch> --no-edit
|
|
29
29
|
|
|
30
|
-
# 2. Bump the version
|
|
30
|
+
# 2. Bump the version — package.json AND the plugin manifest, they must match.
|
|
31
|
+
# rdc-skills-self-test fails the whole run (plugin manifest FAIL) if they drift,
|
|
32
|
+
# and .claude-plugin/plugin.json ships inside the published npm package, so a
|
|
33
|
+
# stale plugin.json version is a real defect in the release, not a lint nit.
|
|
31
34
|
npm version patch|minor|major --no-git-tag-version
|
|
35
|
+
# then hand-edit .claude-plugin/plugin.json's top-level "version" field to match —
|
|
36
|
+
# there is no script for this yet, only the self-test catches drift after the fact.
|
|
32
37
|
|
|
33
38
|
# 3. Commit, tag, and push
|
|
34
|
-
git add package.json
|
|
39
|
+
git add package.json .claude-plugin/plugin.json
|
|
35
40
|
git commit -m "release: v$(node -e \"console.log(require('./package.json').version)\")"
|
|
36
41
|
git tag "v$(node -e \"console.log(require('./package.json').version)\")"
|
|
37
42
|
git push origin master --tags
|
|
@@ -43,6 +48,9 @@ npm view @lifeaitools/rdc-skills version
|
|
|
43
48
|
npm install -g @lifeaitools/rdc-skills@latest
|
|
44
49
|
npm list -g @lifeaitools/rdc-skills --depth=0
|
|
45
50
|
rdc-skills-self-test
|
|
51
|
+
# ^ run this LAST and read the verdict line, not just the section pass counts —
|
|
52
|
+
# a plugin-manifest version mismatch prints as a single top-line FAIL above the
|
|
53
|
+
# skill/guide tables, which all pass independently of it. Exit code 1 on drift.
|
|
46
54
|
```
|
|
47
55
|
|
|
48
56
|
## Public MCP release gate
|
package/commands/deploy.md
CHANGED
|
@@ -155,6 +155,22 @@ _COOLIFY=$(curl -s http://127.0.0.1:52437/v/coolify-api)
|
|
|
155
155
|
curl -s -H "Authorization: Bearer $_COOLIFY" "$DEPLOY_API_BASE/api/v1/applications"
|
|
156
156
|
```
|
|
157
157
|
|
|
158
|
+
**Triggering the actual deploy is different — use the wrapper, not raw curl.**
|
|
159
|
+
`hooks/lib/guard-rules.mjs`'s `coolify-direct` rule blocks a raw curl (or any command whose
|
|
160
|
+
TEXT contains the literal URL) to `/api/v1/deploy` — the deploy-trigger endpoint — on
|
|
161
|
+
purpose, so a production deploy is never one arbitrary curl an agent can fire silently. This
|
|
162
|
+
is NOT a bug to route around with SSH or a differently-worded command
|
|
163
|
+
(`.rdc/lessons/2026-08-07-deploy-coolify-direct-blocks-own-documented-step.md`). The
|
|
164
|
+
sanctioned way to actually trigger a deploy for Mode 1's "Deploy triggered" step is:
|
|
165
|
+
|
|
166
|
+
```bash
|
|
167
|
+
python3 scripts/coolify-deployments.py deploy <application-uuid>
|
|
168
|
+
```
|
|
169
|
+
|
|
170
|
+
Run from the regen-root repo root. Poll `status <deployment-uuid>` (the same script) or
|
|
171
|
+
`GET /api/v1/deployments/<deployment-uuid>` (read-only, not blocked) until `status` is
|
|
172
|
+
`finished`/`failed`/`cancelled` before moving to the gate checks.
|
|
173
|
+
|
|
158
174
|
If clauth daemon is not responding:
|
|
159
175
|
```
|
|
160
176
|
BLOCKED: clauth daemon not responding. Run scripts\restart-clauth.bat, unlock at http://127.0.0.1:52437
|
package/git-sha.json
CHANGED