ci(release): publish semantic releases after main CI - #47
Merged
Conversation
Move release triggering from manually pushed tags to a workflow that runs only\nafter the existing CI workflow succeeds on main. It calculates a stable SemVer\ntag from Conventional Commit messages, creates that tag at the commit CI tested,\nand invokes GoReleaser in the same job. This avoids relying on a tag-push\nworkflow that GITHUB_TOKEN would not trigger.\n\nThe calculator treats feat as minor, fix and perf as patch, and explicit\nbreaking changes as major. Its isolated Git-fixture test is part of CI so a\nfuture edit cannot silently alter release numbering. The serialized release job\nrefreshes tags and refuses to overwrite an existing one.\n\nRequirements: REQ-17.2, REQ-8.5
Point contributors at the automated-release policy, versioning rules, and Homebrew publishing details.\n\nRequirements: REQ-17.2, REQ-8.5
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
Automates stable releases after the existing
CIworkflow succeeds onmain. The workflow calculates a SemVer tag from Conventional Commit messages, creates the tag at the tested commit, and runs GoReleaser in the same serialized job. The version calculator is tested in CI, release policy is documented, and release notes now use the cask installation command.Spec task: tasks.md task 31 — Exercise the release pipeline before tagging.
Requirements covered
brew install --caskcommand.Correctness properties
None.
Deliberately not covered
The existing failed
v0.1.0publication is not mutated by this PR. It requires a deliberate recovery decision because the public tag already exists. The new automation will release future merge commits only when their Conventional Commit type warrants a release.Verification
make release-version-testbash -n scripts/next-version.sh scripts/next-version_test.shgoreleaser checkmake buildmake lintmake tidy-checkmake testmake e2e— not run: no Lima provider, mount, or shell-path changes.Notes for review
feat:makes a minor release,fix:andperf:make a patch release, and atype!:subject orBREAKING CHANGE:footer makes a strict SemVer major release.docs:,test:,chore:, andci:do not release. The job is intentionally CI-gated and creates the tag and GitHub/Homebrew release itself: tags pushed withGITHUB_TOKENdo not trigger a second workflow.