with one click
release
// Release gentle-pi through GitHub and npm. Trigger: release, publish, npm publish, GitHub release, version bump.
// Release gentle-pi through GitHub and npm. Trigger: release, publish, npm publish, GitHub release, version bump.
Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments.
Trigger: judgment day, dual review, adversarial review, juzgar. Run blind dual review, fix confirmed issues, then re-judge.
Use Gentle AI harness discipline for Pi work: clarify first, preserve OpenSpec artifacts, use strict TDD where available, delegate through subagents when useful, and protect review workload.
| name | release |
| description | Release gentle-pi through GitHub and npm. Trigger: release, publish, npm publish, GitHub release, version bump. |
| license | Apache-2.0 |
| metadata | {"author":"gentleman-programming","version":"1.0"} |
Use this skill when preparing, publishing, or verifying a gentle-pi release.
gentle-pi to npm from a local machine..github/workflows/publish.yml so provenance, environment protection, and registry credentials are controlled by GitHub.Inspect state
git status --short
git fetch origin main --tags
git log --oneline --decorate --max-count=5 origin/main
Prepare the release commit
package.json to the next semver version.Verify locally
pnpm test
pnpm publish --dry-run --no-git-checks
The dry run is allowed because it does not publish. It verifies package contents and lifecycle scripts.
Commit and push
git add <intended-files>
git commit -m "<type(scope): release-ready change>"
git push origin HEAD:main
Create the GitHub release
git tag -a v<version> -m "gentle-pi v<version>"
git push origin v<version>
gh release create v<version> \
--repo Gentleman-Programming/gentle-pi \
--title "gentle-pi v<version>" \
--notes "<release notes>"
Publish npm through GitHub Actions
gh workflow run publish.yml \
--repo Gentleman-Programming/gentle-pi \
--ref main \
-f dist-tag=latest
Watch the run and fail the release if it fails:
gh run list --repo Gentleman-Programming/gentle-pi --workflow publish.yml --limit 3
gh run watch <run-id> --repo Gentleman-Programming/gentle-pi --exit-status
Verify npm
npm view gentle-pi@<version> version --registry=https://registry.npmjs.org/
npm dist-tag ls gentle-pi --registry=https://registry.npmjs.org/
If a local npm publish fails, do not retry locally. Use the GitHub workflow instead.
If the workflow fails, inspect logs with:
gh run view <run-id> --repo Gentleman-Programming/gentle-pi --log
If npm verification is briefly stale after a successful workflow, check the exact version first (npm view gentle-pi@<version> version) before assuming publish failed.
Report:
main.latest dist-tag.