ci: add tag-driven release workflow - #1
Closed
makegov-hal[bot] wants to merge 6 commits into
Closed
Conversation
Go SDK for the Tango API — federal contracts, IDVs, entities, opportunities, grants, vehicles, and more, with dynamic response shaping. Ships the full transport, error model, retry/rate-limit handling, webhook signing+CRUD, and a curated subset of resource methods. The sibling SDKs (tango-node, tango-python) are at v1.0.0; this Go SDK starts at v0.1.0 and will grow toward parity in the 0.x line. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
golangci-lint v1.64.8 was choking on Go 1.26 stdlib build-tagged files (chacha20poly1305/fips140only_go1.26.go), cascading into bogus "undefined: tango" typecheck errors against examples/. Linting against the declared minimum Go version (1.23) is also the more conventional choice for OSS — lint what you support. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Pure whitespace — no semantic changes. Caught by the lint job once it got past the Go 1.26 stdlib typecheck cascade. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
- transport.go: defer the standard idiom that errcheck complains about by explicitly discarding the Close error. - testutil_test.go: remove three unused helpers (newTestClientFull, singleResultHandler, singleRecordHandler) and the now-unused net/http/httptest + time imports. The remaining helpers are all in use. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Mirrors the pattern in makegov/docs. Runs fast checks (gofmt, go vet,
end-of-file, trailing-whitespace) on commit, and golangci-lint on push
so contributors catch lint failures locally before CI does.
Local setup:
brew install pre-commit # or: pip install pre-commit
make hooks
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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
force-pushed
the
ci/release-workflow
branch
from
May 15, 2026 18:53
758a8e2 to
a43017c
Compare
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
.github/workflows/release.yml— fires on push of avX.Y.Ztag.proxy.golang.orgsopkg.go.devpicks 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
v0.0.0-testtag to confirm the workflow runs end-to-end.v0.1.0.Risks
GITHUB_TOKEN; no additional secrets required.gh release createfails on the tag — re-run manually withgh release create <tag> --generate-notes. Theproxy.golang.orgpoke is non-fatal (curl errors are swallowed); pkg.go.dev catches up on its own within ~30 min regardless.