@zenuml/core 3.46.5 → 3.46.6
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/skills/ship-branch/SKILL.md +13 -2
- package/dist/stats.html +1 -1
- package/dist/zenuml.esm.mjs +3 -3
- package/dist/zenuml.js +3 -3
- package/package.json +1 -1
|
@@ -56,7 +56,18 @@ On success, the PR is green and ready to merge.
|
|
|
56
56
|
|
|
57
57
|
### Step 4: Land and verify release
|
|
58
58
|
|
|
59
|
-
|
|
59
|
+
Merging to main triggers an npm publish — this is irreversible. To prevent the orchestrator from skipping the land-pr skill's merge strategy logic (which has happened before), **spawn an Agent** for this step:
|
|
60
|
+
|
|
61
|
+
```
|
|
62
|
+
Spawn an Agent with this prompt:
|
|
63
|
+
"Use the Skill tool to invoke the land-pr skill, then follow it to land PR #<PR_NUMBER>
|
|
64
|
+
on mermaid-js/zenuml-core. Follow every step including the merge strategy evaluation.
|
|
65
|
+
Report back the merge SHA and npm version, or the reason it was blocked."
|
|
66
|
+
```
|
|
67
|
+
|
|
68
|
+
Replace `<PR_NUMBER>` with the actual PR number from Step 2.
|
|
69
|
+
|
|
70
|
+
Do NOT run `gh pr merge` directly from the main conversation — the land-pr skill contains merge strategy decision logic that must be evaluated by the Agent.
|
|
60
71
|
|
|
61
72
|
If merge succeeds but npm publish fails, alert immediately with the failure details. Do NOT auto-rollback.
|
|
62
73
|
|
|
@@ -78,7 +89,7 @@ Final report:
|
|
|
78
89
|
- Validation: PASS
|
|
79
90
|
- PR: #<number> (<url>)
|
|
80
91
|
- CI: GREEN (attempt <N>)
|
|
81
|
-
- Merge: SQUASHED into main (<sha>)
|
|
92
|
+
- Merge: <SQUASHED|MERGED> into main (<sha>)
|
|
82
93
|
- npm: @zenuml/core@<version> published
|
|
83
94
|
```
|
|
84
95
|
|