feat(release): automate releases with release-please - #34
Draft
anthonyhaussman wants to merge 5 commits into
Draft
feat(release): automate releases with release-please#34anthonyhaussman wants to merge 5 commits into
anthonyhaussman wants to merge 5 commits into
Conversation
prerelease: true alpha track; tag-separator empty; no v prefix. Assisted-by: GLM 5.2
Anchors release-please state to current package version. Assisted-by: GLM 5.2
release-please job creates tag+release; publish job checks out tag and publishes to npm with alpha or latest dist-tag. Assisted-by: GLM 5.2
Runbook for flipping prerelease flag and cutting stable from the alpha track. Assisted-by: GLM 5.2
Anchor must match current package.json version (1.1.8), not 1.1.7. release-please uses the manifest as the last-released version baseline. Assisted-by: GLM 5.2
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.
Summary
Adds automated release pipeline using release-please-action with an alpha prerelease track interleaved with manual stable promotions.
Deliverables
.release-please-config.json: single-package node config,prerelease: truealpha track, novtag prefix, curated changelog types..release-please-manifest.json: state anchor seeded to1.1.8(matches currentpackage.json)..github/workflows/release-please.yml: runs on push tomain.release-pleasejob opens a pending release PR on Conventional Commits;publishjob is gated onrelease_created, checks out the tag, builds, runs the smoke test, and publishes to npm with--tag alpha(prerelease) or no flag (stable).docs/release-promotion.md: runbook for flipping theprereleaseflag and cutting a stable release from the alpha track.Design
docs/superpowers/specs/2026-07-27-release-please-design.mddocs/superpowers/plans/2026-07-30-release-please.mdVerification
npm run typecheck: passnpm run build: passnpm run smoke:node-import: passOut of scope (per spec)
Post-merge expectation
Merge push triggers
release-please.yml. release-please may open a release PR for1.1.9or1.2.0-alpha.1(thefix:commit on this branch may count as a patch-level bump). If a release PR opens, review and squash-merge it; on that merge release-please cuts the tag, creates the GitHub Release, and thepublishjob pushes to the npmalphadist-tag.Assisted-by: GLM 5.2