@lifeaitools/rdc-skills 0.9.4 → 0.9.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.
- package/package.json +2 -2
- package/skills/release/SKILL.md +20 -4
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@lifeaitools/rdc-skills",
|
|
3
|
-
"version": "0.9.
|
|
3
|
+
"version": "0.9.5",
|
|
4
4
|
"description": "RDC typed-agent dispatch skill suite for Claude Code — plan, build, review, overnight builds",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"claude-code",
|
|
@@ -19,7 +19,7 @@
|
|
|
19
19
|
"type": "plugin",
|
|
20
20
|
"skills": "skills/",
|
|
21
21
|
"guides": "guides/",
|
|
22
|
-
"version": "0.9.
|
|
22
|
+
"version": "0.9.5",
|
|
23
23
|
"commands": "commands/"
|
|
24
24
|
},
|
|
25
25
|
"scripts": {
|
package/skills/release/SKILL.md
CHANGED
|
@@ -126,6 +126,10 @@ rdc:release: regen-root — develop → main
|
|
|
126
126
|
|
|
127
127
|
## Execution Details
|
|
128
128
|
|
|
129
|
+
> **Notification paths by repo type:**
|
|
130
|
+
> - **Public repos** (rdc-skills, clauth): GitHub Actions POSTs to clauth channel on publish — wait for `mcp__claude_ai_clauth__channel_list` event, not a polling loop
|
|
131
|
+
> - **Private repos** (regen-root): Coolify webhook is wired to Supabase — check `deployment_registry` for deploy completion, not the clauth channel
|
|
132
|
+
|
|
129
133
|
### Package repos (clauth, rdc-skills)
|
|
130
134
|
|
|
131
135
|
#### 1. Version bump
|
|
@@ -277,10 +281,22 @@ git push origin develop
|
|
|
277
281
|
- Merge via `mcp__claude_ai_Github_Proxy_MCP__merge_pull_request` with `merge_method: merge`
|
|
278
282
|
|
|
279
283
|
#### 4. Confirm Coolify auto-deploy
|
|
280
|
-
|
|
281
|
-
-
|
|
282
|
-
|
|
283
|
-
|
|
284
|
+
|
|
285
|
+
regen-root is a **private repo**. Coolify's webhook is wired to Supabase — deployment events land there automatically. Do NOT poll the Coolify REST API in a loop. Check Supabase:
|
|
286
|
+
|
|
287
|
+
```sql
|
|
288
|
+
-- Wait for the affected app's deployment to show status = 'finished'
|
|
289
|
+
SELECT slug, last_deploy_at, status, notes
|
|
290
|
+
FROM deployment_registry
|
|
291
|
+
WHERE slug IN (<affected slugs>)
|
|
292
|
+
ORDER BY last_deploy_at DESC;
|
|
293
|
+
```
|
|
294
|
+
|
|
295
|
+
If the registry hasn't updated within 2 minutes of the PR merge, check Coolify directly:
|
|
296
|
+
```bash
|
|
297
|
+
curl -s -H "Authorization: Bearer $(curl -s http://127.0.0.1:52437/v/coolify-api)" \
|
|
298
|
+
"https://deploy.regendevcorp.com/api/v1/applications/<uuid>/deployments?per_page=1"
|
|
299
|
+
```
|
|
284
300
|
|
|
285
301
|
#### 5. Gate checks
|
|
286
302
|
For each affected app, verify: HTTP 200, TLS valid, container running.
|