@mutmutco/kilo-plugin 3.105.0 → 3.105.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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/skills/hotfix/SKILL.md +10 -5
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mutmutco/kilo-plugin",
3
- "version": "3.105.0",
3
+ "version": "3.105.3",
4
4
  "description": "MMI workflow skills and org gates delivery.",
5
5
  "author": {
6
6
  "name": "MMI Future",
package/skills/hotfix/SKILL.md CHANGED
@@ -53,11 +53,16 @@ mmi-cli hotfix start --from <development-pr-number-or-merge-sha> --json
53
53
  ```
54
54
 
55
55
  `hotfix start` resolves the PATCH version, branches from `origin/main`, performs the cherry-pick with `-x`,
56
- prepares Hub distribution artifacts when applicable, pushes the branch, and opens the main-base
57
- PR. Do not duplicate those steps with raw branch commands, manual cherry-picks, or raw GitHub PR creation.
58
-
59
- If the port conflicts, stop and report the conflict. Any behavior change needed to resolve it lands on
60
- `development` first through another normal PR, then starts another hotfix port from that merged fix.
56
+ prepares Hub distribution artifacts when applicable (stamping BOM `sourceCommit` at the durable
57
+ `origin/main` merge-base so a squash merge cannot orphan it — #4361; and for `registry-publish`
58
+ consumers, folds the package version so upgrade probes observe the PATCH), pushes the branch, and opens
59
+ the main-base PR. Do not duplicate those steps with raw branch commands, manual cherry-picks, or raw
60
+ GitHub PR creation.
61
+
62
+ Conflicts confined to regenerable distribution / version-fold paths (e.g. Hub `distribution-bom.json`,
63
+ locked plugin manifests, consumer `package.json`) are auto-resolved and regenerated by the bump step.
64
+ Any other conflict: stop and report. Behavior changes still land on `development` first through a
65
+ normal PR, then start another hotfix port from that merged fix — never hand-resolve onto main.
61
66
 
62
67
  ## 2. Verify the hotfix PR
63
68