Skip to content

ci: release by itself on every merge to main that carries a feat, fix or perf commit - #14

Merged
ECG-Rudy-Glt merged 1 commit into
mainfrom
ci/auto-release
Nov 4, 2026
Merged

ECG-Rudy-Glt merged 1 commit into
mainfrom
ci/auto-release

Conversation

@ECG-Rudy-Glt

Copy link
Copy Markdown
Owner

Until now a release needed someone to push a tag by hand, and v0.3.1 was already 6 commits behind main.

On every push to main the release workflow now: runs gofmt, vet and tests; computes the next version from the conventional commits since the last tag (feat: minor, fix:/perf:/revert: patch, ! or BREAKING CHANGE: minor before 1.0.0 and major after); pushes the tag; runs goreleaser (binaries and checksums.txt). docs:, chore:, test:, ci:, refactor: alone release nothing. A tag pushed by hand still works. CONTRIBUTING documents it.

A tag pushed with the workflow token does not start another workflow, so tagging and goreleaser run in the same job.

Checked locally on the real history without tagging anything: this repo would become v0.3.2; synthetic histories give no release for docs:/chore:, a patch for fix:, a minor for feat: and feat!: (0.x).

Merging this releases v0.3.2 right away, since main already carries fixes since v0.3.1.

@ECG-Rudy-Glt
ECG-Rudy-Glt merged commit 8bf62a5 into main Nov 4, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant