Skip to content

Standard gated npm publish flow + @persona-engine/core 0.2.1 (#42) - #43

Merged
shojikumaru merged 2 commits into
mainfrom
feat/42-npm-standard-flow
Aug 23, 2026
Merged

Standard gated npm publish flow + @persona-engine/core 0.2.1 (#42)#43
shojikumaru merged 2 commits into
mainfrom
feat/42-npm-standard-flow

Conversation

@shojikumaru

Copy link
Copy Markdown
Member

Closes #42.

Adds the org-standard release path (proven today on meetmate/context-kit/sitter): workflow_dispatch + npm-publish environment gate + --provenance, token-less from the first dispatch (the package already exists, so npm trusted publisher/OIDC is wired before dispatch — no NODE_AUTH_TOKEN secret exists in this repo).

Monorepo notes: the npm package root is packages/core (workspace), so npm's root-README force-inclusion traps do not apply; files allowlist already present. Workflow runs npm citypecheckvitest (375 tests, green locally) → workspace build → version check → publish from packages/core.

Version: 0.2.1 (npm is at 0.1.0 while the repo shipped v0.2.0 on 2026-08-21; 0.2.1 because this bump commit postdates tag v0.2.0). After merge: tag v0.2.1 + Release (T-5), then dispatch + Sho approval + npm view / CONTENT_IDENTICAL verification.

Review: 5-seat release-gate (writer=Alpha config-only diff; seats kimi/glm/grok/gemini/codex-sol per loom-seats) runs on this PR before merge.

🤖 Generated with Claude Code

…/core to 0.2.1 (#42)

- .github/workflows/publish.yml: workflow_dispatch + npm-publish environment
  gate + provenance, token-less (npm trusted publisher / OIDC), version==
  packages/core/package.json check, concurrency guard
- packages/core: 0.1.0 -> 0.2.1 (npm was one release behind the repo's v0.2.0;
  0.2.1 because the bump commit postdates tag v0.2.0)
- package-lock.json: synced workspace version ref

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@github-actions github-actions Bot added the needs-risk-review Machine-applied: high-risk paths touched; human roster review required label Aug 23, 2026
…s a workspace-keyed object in a workspace child (GLM seat B1)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@shojikumaru

Copy link
Copy Markdown
Member Author

5-seat release-gate review record (writer=Alpha, config-only diff)

Panel per loom-seats (--size S --risk release-gate --absent fable-5 --absent opus-5, writer-same-family opus excluded): kimi-k3 / glm-5.3 / grok-4.6 / gemini-3.7-flash / codex-sol.

r1 at c7f54f0: GO×2 (kimi: 5 attack lines clean by execution; gemini: static clean) / NO-GO×3 — glm, grok, codex independently converged on the same blocker: npm pkg get version returns a workspace-keyed object inside packages/core, so the version-check step could never pass (fail-closed DOA). Orchestrator reproduced: npm pkg get version in packages/core → {"@persona-engine/core": "0.2.1"} (npm 11.17.0/node 26). grok additionally flagged the not-yet-created npm-publish environment (correct; it is the planned pre-dispatch owner step).

Fix f98e3d5: read the manifest directly (node -p "require('./package.json').version") — glm's own verified suggestion.

Delta (glm, blocker owner): GO at f98e3d5 — fixed step exits 0 on 0.2.1 / exits 1 on 0.2.0 (run-block extracted byte-identical from the workflow); delta touches only that step + comment; old command still reproduces the blocker in a control.

Full seat outputs archived in session scratchpad (seats/pe43/*/out.md). Note for the record: the orchestrator pushed the fix commit while grok/codex were still reading the shared clone (HEAD moved mid-review) — their r1 verdicts were interpreted against c7f54f0 accordingly.

Remaining before dispatch (owner): risk-reviewed label on this PR → merge → tag v0.2.1 + Release → create npm-publish environment → wire trusted publisher on the existing @persona-engine/core → dispatch 0.2.1 → approve.

@shojikumaru shojikumaru added the risk-reviewed Human roster approval for the current head SHA (auto-stripped on new push) label Aug 23, 2026
@shojikumaru
shojikumaru merged commit 929b3ea into main Aug 23, 2026
19 of 20 checks passed
@shojikumaru
shojikumaru deleted the feat/42-npm-standard-flow branch August 23, 2026 16:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-risk-review Machine-applied: high-risk paths touched; human roster review required risk-reviewed Human roster approval for the current head SHA (auto-stripped on new push)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Re-align npm with repo releases: publish @persona-engine/core 0.2.x via the standard gated flow

1 participant