midnite-release-complete

Run this Skill on the release/vX.Y.Z branch after human review. It verifies preconditions, shows the full tag and publish plan for explicit confirmation, then creates annotated tags, pushes them, merges the release PR to main, and verifies the published Release.

The branch must be release/vX.Y.Z with a clean tree, package versions must match the branch, the changelog must contain a dated section for that version, the RELEASES_REPO_TOKEN secret must exist, and moon ci must pass. Any failure stops the flow before changes occur.

Yes, pass 'ephemeral' from main to create a test release. It tags HEAD, pushes to trigger packaging to the public apps repo, skips the PR and merge, and provides teardown commands to delete the release, tag, and reset version.json afterward.

The source repo is private, so public-facing artifacts live in bilo-io/midnite-apps. Source tags stay in the private repo while the Release, installers, update feeds, and changelog mirror are published under namespaced tags like midnite-studio/vX.Y.Z in the public repo.

The Skill reports exactly what landed — whether the tag was created, pushed, or merged — so a human can finish manually. It never silently retries a partial publish, and nothing is irreversible before the first tag push.

Tags come from the repo's fixed planRelease function, producing a lockstep vX.Y.Z tag when all packages share a major.minor version, or scoped [email protected] tags for patch releases. For a first release with no prior tags, it tags the versions already in the tree.