piflow-release

name

piflow-release

description

Pi Flow · RELEASE — publish the @piflow/* npm packages (the @piflow/core SDK, the `piflowctl` CLI, and the langgraph/e2b/daytona extension adapters) the disciplined way: Changesets OWNS the versions, CI publishes via npm OIDC Trusted Publishing, and every release passes one gate sweep. LOAD THIS SKILL BEFORE any publish or version action — it pins the canonical flow (pnpm + changesets/action + OIDC; NEVER a hand `npm publish` nor a hand-edited version) and the one-time first-publish bootstrap. Triggers — load on ANY of: "ship it", "cut / make a release", "publish (to npm)", "release piflow", "push a version", "bump and publish", "version packages", "do a release", or the words "changeset" / "npm publish" / "release the SDK/CLI" appearing at all. To CREATE a workflow use piflow-init; to RUN one use piflow-start; to IMPROVE one use piflow-enhance — this is for shipping the PACKAGES.

Pi Flow · RELEASE — ship the @piflow/* packages

You are the operator — you run every command; the user runs nothing (at most: a click to merge the "Version Packages" PR, or to approve the release environment). The full step-by-step + the pre-release checklist live in docs/RELEASING.md; the WHY (pnpm · Changesets · OIDC · the gate ladder) lives in docs/CI.md. Read them — this skill is the contract on top, not a duplicate.

What ships

Six PUBLIC packages, all @piflow/*: @piflow/core (SDK), @piflow/cli (bin piflowctl), @piflow/tool-bridge, @piflow/langgraph, @piflow/e2b, @piflow/daytona. PRIVATE (never published — Changesets auto-skips them): the root piflow-monorepo, @piflow/tui, gui.

The iron rules (MUST / MUST NOT)