Switch release workflow to manual dispatch with releaseforge#7
Merged
Conversation
Replace the push-tag trigger with workflow_dispatch (optional tag input). The workflow now auto-bumps the version from conventional commits via releaseforge, generates AI release notes, creates and pushes the tag, then runs GoReleaser — mirroring the seedstorm release flow. Requires a GEMINI_API_KEY repo secret for the release-notes step.
use-git-fallback already defaults to true; set it explicitly so the workflow self-documents that a missing GEMINI_API_KEY degrades to git commit-log notes rather than failing the release.
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.
What
Converts the release workflow from a tag-push trigger to a manual
workflow_dispatch, mirroring seedstorm's flow.Before, releasing meant manually creating and pushing a
v*tag. Now you click Run workflow in the Actions tab (optionally typing a tag); the workflow handles versioning, notes, tagging, and publishing.Flow
make buildthengo test ./... -v, so integration tests actually run against the binary).AxeForging/releaseforge→bump: compute the next version from conventional commits.taginput if provided, else the auto-bumped version.AxeForging/releaseforge→generate: AI release notes via Gemini.Requires
GEMINI_API_KEYsecret in the pipekit repo (used by the notes step), as seedstorm has. Without it thegeneratestep fails.GITHUB_TOKENis provided automatically.Note
This drops the automatic
push: tags: 'v*'trigger — releases are now manual-dispatch only, matching the other tools.