Repository navigation
Add the shared Go release workflow - #27
Merged
Merged
Conversation
One reusable pipeline for every Go project: build the binaries and publish them on the GitHub release only, on a version tag or on request. It refuses a GoReleaser config that publishes anywhere else, takes the notes from the CHANGELOG, mirrors the src/ module tag and attests provenance. A caller template and stdlib tests come with it.
This was referenced Nov 13, 2026
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.
Summary
The one release pipeline for every Go project in every Simtabi-owned org (owner, 2026-11-13: GitHub-based binaries only, built on a tag or on request, kept somewhere reusable and shareable). This repository is public, so callers in ichava, sangehq, laranail and simtabi can all use it.
.github/workflows/go-release.yml(workflow_callonly): checks the tag isvX.Y.Z[-pre]and on GitHub; checks out the tag; refuses a GoReleaser config holding any other channel (brews,homebrew_casks,scoops,winget,chocolateys,aurs,aur_sources,snapcrafts,flatpaks,nix,dockers,dockers_v2,docker_manifests,docker_signs,kos,krews,npms,cloudsmiths,furies,publishers,blobs,uploads,artifactories); takes the release notes from the tag's CHANGELOG section (fails closed); mirrors thesrc/vX.Y.Zmodule alias tag; runs GoReleaser; reads the published notes back; runs an optional caller post-release command for extra assets; attests provenance forchecksums.txtand any extra checksums.GOPRIVATEkeeps the build off the public Go proxy.templates/go/release.yml: the caller every Go repo copies. Triggers are a pushed version tag, orworkflow_dispatchwith ataginput; one run per tag, never cancelled.go-release/tests/(stdlib only, run by CI): the workflow is only callable, the tag is required, the channel list is exactly the full list, and the template triggers only on a version tag or a dispatch naming one. Each of three planted defects (a branch push, a missing channel, apushtrigger on the shared workflow) turns it red.go-release/README.md, linked from the README.Verification
python3 -m unittest discover -s go-release/tests -v: 7 passed.go-release.yml,ci.ymland the template.