package-releaselisted

# Package Release Framework-maintainer workflow for releasing OpenPress packages. Use this only in the OpenPress framework repo, not downstream workspaces. ## Responsibilities - Inventory local release-bound changes before staging or opening a PR. - Check active docs and bundled skills for stale release-facing guidance. - Confirm changeset coverage for package-affecting changes. - Write release PRs with concrete scope and verification. - Merge the generated Changesets version PR when the release is ready. - Monitor GitHub Actions and verify npm/GitHub Releases after publish. ## Preflight Run: ```bash git status --short git branch --show-current git remote -v gh auth status gh repo view --json nameWithOwner,defaultBranchRef ``` If the worktree is mixed, stage explicit paths only. Do not stage generated output such as `public/openpress/`, `dist-react/`, `.deploy/`, `.openpress/`, or temporary scripts. ## Local Change Inventory Classify the diff before writing a PR: ```bash git diff --stat git diff --name-only find .changeset -maxdepth 1 -type f -name "*.md" ! -name README.md -print ``` Expected buckets: - runtime/framework: `packages/core/` - CLI/scaffold: `packages/cli/`, `packages/create/` - landing/docs: `apps/web/`, `docs/` - bundled skills: `skills/` - dogfood verification: `press/`, `tests/press-lint.test.mjs` Package-affecting changes need a changeset. Docs-only or skill-only changes may skip npm release unless they are intentionally part of a package releas