docs(skill): document the CLI release process#47
Open
hbrooks wants to merge 1 commit into
Open
Conversation
Add a maintainers section to the ellipsis skill covering how the CLI is released: Homebrew-tap-only distribution (never npm), the tag-triggered release.yml automation, and the manual bump/commit/tag steps. Records that package.json is the version source of truth and the tag must match.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Documents how the CLI is released, in the
ellipsisskill so it lives with the rest of the CLI knowledge. There was no written record of the release process before.Why
Came out of a "how do we automate the release?" question. The build-and-publish half is already fully automated on tag push; the only manual part is the version bump + tag. This captures both so the process is discoverable.
Content added
A "Releasing the CLI (maintainers)" section covering:
package.jsonisprivate, has nobin, nopublishConfig. The onenpm versioncall in the workflow is just a local version-bump tool, not a registry publish.release.ymlautomation on avX.Y.Ztag push (plus theworkflow_dispatchfallback): stamp version, cross-compile the four platform binaries, checksums, GitHub release, regenerate + push the Homebrew formula.package.jsonis the version source of truth (src/lib/constants.tsinlinespkg.version).package.json,chore(release): vX.Y.Zcommit, then create + push the matching tag. Tag version must equalpackage.jsonversion because the formula'stest doassertsagent --version.Docs-only; no code changes.