Skip to content

ci: add tag-driven release workflow - #3

Merged
infinityplusone merged 1 commit into
mainfrom
ci/release-workflow
May 15, 2026
Merged

ci: add tag-driven release workflow#3
infinityplusone merged 1 commit into
mainfrom
ci/release-workflow

Conversation

@makegov-hal

@makegov-hal makegov-hal Bot commented May 15, 2026

Copy link
Copy Markdown

Summary

  • Adds .github/workflows/release.yml — fires on push of a vX.Y.Z tag.
  • Runs the test suite one last time, creates a GitHub Release with auto-generated notes, then pokes proxy.golang.org so pkg.go.dev picks up the new version promptly.

Why now (and why a separate PR)

Held back from the initial commit so we could land it deliberately and confirm the tag flow. The Go release pattern is just different enough from the sibling SDKs' npm/PyPI publish workflows that it's worth a focused review.

Testing

  • After merge, push a throwaway v0.0.0-test tag to confirm the workflow runs end-to-end.
  • Delete the test tag + release.
  • First real run will be v0.1.0.

Risks

  • Uses only the built-in GITHUB_TOKEN; no additional secrets required.
  • Worst case if it breaks: gh release create fails on the tag — re-run manually with gh release create <tag> --generate-notes. The proxy.golang.org poke is non-fatal (curl errors are swallowed); pkg.go.dev catches up on its own within ~30 min regardless.

Fires on push of a vX.Y.Z tag:
- runs the test suite one last time
- creates a GitHub Release with auto-generated notes
- pings proxy.golang.org so pkg.go.dev picks up the new version

No secrets beyond the built-in GITHUB_TOKEN.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@infinityplusone
infinityplusone merged commit 50f313a into main May 15, 2026
5 checks 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