@groeponline/pi-wishcraft 0.23.1 → 0.23.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/CHANGELOG.md CHANGED
@@ -2,8 +2,17 @@
2
2
 
3
3
  ## [Unreleased]
4
4
 
5
+ ## [0.23.2] - 2026-08-20
6
+
7
+ ### Fixed
8
+ - Release workflow creates a GitHub Release for each tag so the Releases page Latest matches npm.
9
+
5
10
  ## [0.23.1] - 2026-08-20
6
11
 
12
+ ### Fixed
13
+ - Per-segment fault isolation: a throwing custom `command` segment shows `!id` instead of blanking the footer.
14
+ - `open_ports` parses macOS netstat dot-separated local addresses (`*.5900`, `127.0.0.1.631`).
15
+
7
16
  ## [0.23.0] - 2026-08-20
8
17
 
9
18
  ### Added
package/RELEASE.md CHANGED
@@ -20,11 +20,12 @@ verify it.
20
20
  **Default:** every merge to `main` is a release. `.github/workflows/release.yml`
21
21
  runs `node scripts/release.mjs auto --push` on `main` and publishes in that
22
22
  same job (`scripts/npm-publish.sh`) with the GroepOnline org secret
23
- `NPM_TOKEN`. A tag pushed with `GITHUB_TOKEN` does **not** start another
24
- workflow, so publish cannot wait for the tag event. Manual SSH/PAT tag
25
- pushes still run the tag job. `auto` reads commit subjects since the last
26
- `v*` tag: `feat:` minor, `feat!:` / `BREAKING CHANGE` major, otherwise
27
- patch.
23
+ `NPM_TOKEN`, then creates a GitHub Release for the tag
24
+ (`scripts/github-release.sh`) so the Releases page Latest matches npm. A tag
25
+ pushed with `GITHUB_TOKEN` does **not** start another workflow, so publish
26
+ cannot wait for the tag event. Manual SSH/PAT tag pushes still run the tag
27
+ job. `auto` reads commit subjects since the last `v*` tag: `feat:` → minor,
28
+ `feat!:` / `BREAKING CHANGE` → major, otherwise patch.
28
29
 
29
30
  The first merge after `v0.18.0` therefore becomes **0.19.0** (the 0.19
30
31
  `feat:` commits are already on `main`). Later docs/fix merges become
@@ -78,6 +79,7 @@ start a second run.
78
79
  7. `npm run verify:package` (catalog contract gate — see `scripts/verify-package.mjs`)
79
80
  8. `node scripts/release.mjs auto --push` (main only)
80
81
  9. `sh scripts/npm-publish.sh` with `NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}` (fail-closed `npm view`, idempotent skip, then the Pi catalog URLs)
82
+ 10. `sh scripts/github-release.sh` with `GITHUB_TOKEN` (idempotent: skip if that tag already has a Release; notes from `CHANGELOG.md`)
81
83
 
82
84
  `NPM_TOKEN` is the GroepOnline **org** Actions secret (publish rights to the
83
85
  `@groeponline` scope). This repo has no override; Actions inherits the org
@@ -109,10 +111,14 @@ gh run view <databaseId> --repo GroepOnline/pi-wishcraft \
109
111
  # 4. npm registry (published + propagated)
110
112
  npm view @groeponline/pi-wishcraft version # 0.15.0
111
113
  npm view @groeponline/pi-wishcraft dist-tags # { latest: '0.15.0' }
114
+
115
+ # 5. GitHub Release Latest matches npm
116
+ gh release list --repo GroepOnline/pi-wishcraft --limit 5
112
117
  ```
113
118
 
114
- A release is "done" when all four hold: local green, tag on origin, CI
115
- `success`, and `npm view` returns the new version.
119
+ A release is "done" when all five hold: local green, tag on origin, CI
120
+ `success`, `npm view` returns the new version, and GitHub Releases Latest
121
+ is that same tag.
116
122
 
117
123
  ## Known gotchas
118
124
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@groeponline/pi-wishcraft",
3
- "version": "0.23.1",
3
+ "version": "0.23.2",
4
4
  "description": "Wishcraft cockpit for the pi coding agent — powerline status, vibes, idea inbox, bash mode, and full customization.",
5
5
  "type": "module",
6
6
  "files": [