chore(release): replace release-please with cut-release.sh - #38
Merged
Merged
Conversation
release-please kept a manifest of state separate from the git tags, and the two
desynced: the 2.3.0 release PR merged but the tag was never created, so release-please
lost its anchor, regenerated the whole changelog (with duplicate entries from the
restructure's rewritten history), and re-counted the long-shipped v2.0.0 facade change
as breaking → a phantom 3.0.0. It also needed a special repo setting and a bolt-on
major-alias mover.
cut-release.sh does the whole thing in one deterministic, local command:
- current version = the latest vX.Y.Z tag (the only source of truth — can't desync)
- CHANGELOG section from conventional commits since that tag (lastTag..HEAD only,
so the full-history duplicates can't recur)
- commit + tag + push + GitHub release + advance the vN alias
- refuses a non-major bump when it sees a breaking commit (semver can't slip)
Keeps commitlint (it keeps commits parseable for the changelog). Removes the
release-please workflow, config, and manifest.
CMaintz
force-pushed
the
chore/replace-release-please
branch
from
September 29, 2026 10:33
32af2ac to
72de006
Compare
- run(): eval "$*" not eval "$@" (SC2294) - require_clean_main: explicit if, not A && B || C (SC2015) - next_version: shellcheck-disable the deliberate IFS=. word-split (SC2086)
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.
release-please kept state (a manifest) separate from the git tags, and they desynced: the 2.3.0 release PR merged but the tag was never created, so release-please lost its anchor, regenerated the entire changelog (with duplicate entries from the restructure's rewritten history), and re-counted the long-shipped v2.0.0 facade change as breaking → a phantom 3.0.0 (#35). It also needed a special repo setting (Actions-can-create-PRs) and a bolt-on major-alias mover.
scripts/cut-release.shreplaces it — one deterministic, local command:bash scripts/cut-release.sh minor # major | patch | X.Y.Z ; --dry-run to previewvX.Y.Ztag (the only source of truth — nothing to desync)CHANGELOGsection built from conventional commits since that tag only (so the full-history dupes can't recur)gh release create+ advance thevNaliasExercised locally: version math (patch/minor/major), breaking-detection, and changelog grouping all verified.
Keeps commitlint — it keeps commits parseable so the changelog generation works (drop it later if you want). Removes the release-please workflow + config + manifest.