Kitup release
Use when preparing or publishing a kitup release, including release branch preparation, version bumps, manual PR handoff, manual tags, GitHub Actions publishing, and public smoke checks.From its SKILL.md
npx -y skills add lathe-cli/kitup --skill kitup-releaseAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 7 commands, including `make release-patch` and 6 more.
SKILL.md
1.5 KB, 329 tokens by cl100k_base, as published. Nobody here has run it
kitup Release
Use this only inside /Users/x/git/samzong/kitup or the upstream kitup repository.
Release Contract
Do not publish from a pull request. Do not tag the release branch.
The maintainer-owned flow is:
- Start from a clean, up-to-date
main. - Run one release prep command:
make release-patch
make release-minor
make release-major
- Let the command create
release/vX.Y.Z, update versions, runmake check, and commitchore: prepare vX.Y.Z release. - Ask the maintainer to open and merge the release PR manually.
- After merge, the maintainer tags
mainmanually:
git checkout main
git pull --ff-only
git tag vX.Y.Z
git push origin vX.Y.Z
Version Surfaces
Release prep must keep these in sync:
ts/package.jsonrust/Cargo.tomlrust/Cargo.lockexamples/rust/Cargo.lockgo-cobra/go.mod
Automation
The root vX.Y.Z tag triggers .github/workflows/release.yml. The workflow runs make check, verifies package versions, publishes npm and crates.io packages, creates go/vX.Y.Z and go-cobra/vX.Y.Z, creates GitHub Release notes, and runs scripts/smoke-release.sh X.Y.Z.
If a registry already accepted a version, do not delete and recreate tags without an explicit recovery plan.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.