@mutmutco/pi-plugin 4.3.62 → 4.3.63
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
|
@@ -89,7 +89,12 @@ A release announces itself in Slack once its deploy and publish are green: the H
|
|
|
89
89
|
project channel when the project's registry META sets `releaseChannel`; never post release notes
|
|
90
90
|
by hand. The Hub always needs a curated `--announce-summary-file`, and so does any product whose
|
|
91
91
|
META sets `releaseChannel` — 3–6 plain lines in the project's `releaseLanguage` (default `en`),
|
|
92
|
-
written for that project's audience, never the raw PR titles.
|
|
92
|
+
written for that project's audience, never the raw PR titles. Every summary line must describe work
|
|
93
|
+
that actually ships in the cut: the train refuses an issue or PR number the release range carries in no
|
|
94
|
+
commit, so build and verify the lines from one pass over that range —
|
|
95
|
+
`git log --stat --format='%h %s%n%b' origin/main..origin/development`, which carries each commit's
|
|
96
|
+
subject, body and changed files — never from subjects, PR titles or memory; a line whose claim is not
|
|
97
|
+
in that output does not go in the file.
|
|
93
98
|
|
|
94
99
|
Announcement delivery uses the developer's GitHub-authenticated Hub session. The Hub checks project
|
|
95
100
|
authority, resolves the registered channel, and reads the MMI Future Slack key inside its vault boundary.
|
package/skills/release/SKILL.md
CHANGED
|
@@ -33,7 +33,7 @@ Read `ready`, then `findings[]`: each carries `code`, `severity` (`blocker` · `
|
|
|
33
33
|
|
|
34
34
|
Run from the primary checkout on the lane's start branch (`rc`; `development` for direct-track and `--dev`). Export the bump intent once from the bare argument — `MMI_BUMP_INTENT=minor|major|patch`, unset → `patch`; `MMI_RELEASE_VERSION=X.Y.Z` only for an exact target the tag math cannot derive.
|
|
35
35
|
|
|
36
|
-
Two cases need a summary file. (1) **MMI-Hub** — always: write a fresh 3–6 line neutral summary to `f=$(mkdir -p .jerv/tmp && mktemp .jerv/tmp/release-summary.XXXXXX)` — sourced from
|
|
36
|
+
Two cases need a summary file. (1) **MMI-Hub** — always: write a fresh 3–6 line neutral summary to `f=$(mkdir -p .jerv/tmp && mktemp .jerv/tmp/release-summary.XXXXXX)` — sourced from the range `origin/main..origin/development`, rewritten in Hub-subsystem terms, never a product or brand name. Hub scope is only `mutmutco/MMI-Hub`: never a product's board, `ds-propagate.yml`, or a product's deploy state. **Build and verify every line from ONE command's output**, never from commit subjects or PR titles alone: `git log --stat --format='%h %s%n%b' origin/main..origin/development` gives each commit's subject, its full body (where a bundled PR records `Closes #N`) and the files it changed in a single pass. A line whose claim you cannot point to in that output does not go in the file, and every `#N` a Hub line cites must appear there: the train refuses `--apply` on a citation that ships in no commit of the cut. (2) **Any product repo whose META carries `releaseChannel`** (`mmi-cli oracle org project get {owner}/{repo} --json`) — required too: read `releaseLanguage` (default `en`) and write 3–6 lines IN THAT LANGUAGE, in plain words for the project's audience: what changed and why it matters to a user; no commit prefixes, no issue or PR numbers, no file names, no product-internal jargon. The train refuses `--apply` without the file, and raw release notes are never posted to a project channel. A repo with no `releaseChannel` announces nothing and needs no file.
|
|
37
37
|
|
|
38
38
|
```bash
|
|
39
39
|
mkdir -p .jerv/tmp
|