feat(release): automate version + tag via release-please#8
Merged
Conversation
Wires up googleapis/release-please-action@v4 so that conventional-commit history on `main` drives a "Release vX.Y.Z" PR. Merging that PR creates the tag + GitHub release, which triggers the existing release.yaml → goreleaser → cask publish to RefuseHQ/homebrew-tap. Bootstrapped at 0.0.0; release-please will propose the first real version on the next push to main (likely 0.1.0 given the feat: commits in history). CHANGELOG.md reset to a clean header — release-please manages future entries from commit messages. Note: for the chain to fire end-to-end without manual intervention, the release-please workflow needs a PAT (RELEASE_PLEASE_TOKEN) with `contents: write` on this repo. With only GITHUB_TOKEN, the tag is created but downstream release.yaml does not fire (GitHub policy on token-cascaded workflows). The workflow uses the PAT if present and falls back to GITHUB_TOKEN otherwise.
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
Wires up release-please so conventional-commit history on `main` drives a "Release vX.Y.Z" PR. Merging that PR creates the tag + GitHub release, which triggers the existing `release.yaml` → goreleaser → cask publish to `RefuseHQ/homebrew-tap`.
End-to-end flow after this merges:
No more manual `git tag`.
Files
Required follow-up
For tag pushes by release-please to trigger the existing release.yaml workflow, set a `RELEASE_PLEASE_TOKEN` secret with a PAT that has `contents: write` on this repo. (GitHub policy: workflows triggered by `GITHUB_TOKEN` don't cascade into other workflows.) The workflow falls back to `GITHUB_TOKEN` if the secret is absent, in which case the release PR opens but the downstream binary publish needs to be re-kicked manually.
Test plan