@gcunharodrigues/wrxn 0.20.1 → 0.20.2

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
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@gcunharodrigues/wrxn",
3
- "version": "0.20.1",
3
+ "version": "0.20.2",
4
4
  "description": "WRXN Kernel — installable AI operating system. Two profiles (project | workspace), pull-based updates, managed/seeded/state file classes.",
5
5
  "bin": {
6
6
  "wrxn": "bin/wrxn.cjs"
@@ -25,6 +25,11 @@ are global slash-skills with no local file; the promote is yours). Follow these
25
25
  opens a PR, and arms auto-merge (`gh pr merge --auto --squash`) — no settings file, no env flag, no
26
26
  GitHub clicks. `--branch` defaults to the current branch; pass `--base` if the trunk is not `main`.
27
27
  Run `wrxn ship --dry-run` first if you want to preview the exact promote plan before it runs.
28
+ - **Multi-issue PR bodies — one closing keyword PER issue.** When the PR resolves more than one
29
+ issue, write a closing keyword before EACH number (`Closes #104, closes #105`, or one `Closes #N`
30
+ per line). GitHub auto-closes only the issue directly after a keyword, so a comma/`+` list after a
31
+ single keyword (`Closes #104, #105`) closes ONLY the first — trailing slices leak open (real: PR
32
+ #106 left #105 open). Applies on squash-merge too (GitHub reads the PR body + the squash message).
28
33
  3. **Confirm auto-merge is armed** (e.g. `gh pr view --json autoMergeRequest` shows it enabled). The
29
34
  server-enforced CI ruleset is now the authority: GitHub merges to the trunk the instant CI is green.
30
35
  You never merge by hand and you never push directly to the trunk.