Repository navigation
feat(go): Split release pipeline jobs - #17
Merged
Merged
Conversation
Go releases can now isolate validation, artifact building, and publication. Only the final job receives write access, so tests and build commands cannot publish repository changes.
nfebe
force-pushed
the
feat/go-release-workflow
branch
from
September 2, 2026 17:15
93c5345 to
3482b7d
Compare
A release can now resume when its tag already identifies the same commit. Missing configured artifacts stop publication instead of producing an incomplete 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
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.
Add a reusable Go release workflow that runs validation, artifact building, and publication as separate jobs. Only publication receives repository write access.