// Prepare or verify releases for this Pi monorepo. Use for Changesets, pnpm lockfile/versioning, package preview generation, release-age policy, or published package installability checks.
Compare proposed Pi customisation features with Pi built-in primitives before implementation. Applies to extensions, packages, slash commands, workflows, or speculative feature ideas.
Build or modify packages in this Pi monorepo. Use when creating Pi extensions, prompt shims, built-in extension wiring, package scaffolds, or packages/pi-* implementation work.
Use when verifying that published Pi packages from this repository install and load for normal Pi users without the repository wrapper. Applies to pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.
Validate Pi monorepo changes before reporting. Use after editing TypeScript, Svelte, package manifests, built-in registry, tests, or repo tooling.
| name | pi-release-workflow |
| description | Prepare or verify releases for this Pi monorepo. Use for Changesets, pnpm lockfile/versioning, package preview generation, release-age policy, or published package installability checks. |
| compatibility | Requires this Pi coding-agent monorepo release workflow. |
Use this when preparing, validating, or debugging package releases from this repo.
minimumReleaseAge; do not blindly bypass it for
fresh registry packages.pnpm-workspace.yaml or package
manifests intentionally, then run pnpm install to refresh the
lockfile.pnpm changeset status for pending release intent.pnpm install --frozen-lockfile to verify committed lockfile state.pnpm run preview:generate when preview image output should change.pnpm run check before release PRs or publishing.pi-package-sandbox-test for normal-user install/load
validation of published Pi packages.pnpm update -r --latest --catalog is not the safe catalog workflow
here.minimumReleaseAgeExclude;
that applies to registry packages.pnpx only when
appropriate.