Release 0.3.1 - #20
Merged
Merged
Conversation
Documentation only. Two commits corrected the bundled skill: one stated that the model and thinking level are chosen once per run, the other named `changes.omitted` as where the reason for a skipped write check lives and gave the condition that prevents the check from running at all. No Go code changed, no JSON contract changed, and no flag was added, so this is a patch bump. The release exists because the skill ships through npm postinstall: both corrections sat on main reaching nobody, while every session kept reading the text they fix. The `0.2.0` strings in `npm/test/release-metadata.test.mjs` and `ARCHITECTURE.md` are untouched on purpose — the first are fixtures for the tag-versus-package-version check, the second is another package's published version.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation only, so this is a patch bump. Two commits corrected the bundled
skill since
0.3.0:b4ddb59(PR docs: state that the model is chosen once per run #18) — the skill showed--modelonce in its command blockbut never said the choice is run-level, while step 3 spoke of preserving
"every explicit model" and step 5 offered one to three workers. A reader
combining those infers one model per worker and writes
--modeltwice, whichthe CLI rejects before anything runs.
fd19494(PR docs: point the caller at the reason a write check skipped #19) — the run document has carried a rootchangesfieldsince the manifest shipped, and the skill never named it. An orchestrator that
read
writes: {"skipped": "change manifest unavailable"}had no way from thatfile to learn which unavailability it hit, so it hand-verified every changed
path instead. Step 5 also gains the condition that prevents the check from
running: the manifest is measured against the state recorded before the first
worker started, so an already-dirty workspace has no clean base.
No Go code changed, no JSON contract changed, and no flag was added. The release
exists because the skill ships through npm postinstall: both corrections sat on
mainreaching nobody, while every session kept reading the text they fix.Version identity
package.json,package-lock.json(both entries), and thego installline indocs/v0-usage.md. The0.2.0strings innpm/test/release-metadata.test.mjsand
ARCHITECTURE.mdare untouched on purpose: the first are fixtures for thetag-versus-package-version check, the second is
pi-subagent-bridge's publishedversion.
Local snapshot gate
Run in full at this commit, per
docs/releasing.md:npm ci --ignore-scriptsthennpm run verify— exit 0go run ./tools/releaseproduced the four native archives with prefixpi-worker_v0.3.1_, andshasum -a 256 -c checksums.txtverified all fournpm run stageplus the stagedcurrent checkout npm packassertion passednpm packproduced exactlypi-worker-0.3.1.tgz; the binary inside stampsv0.3.1with this commit, and the packedskills/pi-worker/SKILL.mdcarriesboth corrections
After merge the release starts from the matching
v0.3.1tag push and publishesthrough OIDC; no token is involved.