Summary

• add Go to the existing integration release workflow's manual-dispatch interface
• validate and test a Go integration before creating its module-scoped tag and GitHub Release
• verify published modules through proxy.golang.org and document the ADK release flow
• harden release input parsing before values reach shell commands

Motivation / context

Go integrations in this monorepo need independently versioned tags such as integrations/adk/go/v0.1.0. Unlike PyPI and npm publishing, the tag itself publishes a Go module, so the workflow must run checks before it creates the tag.

Impact

Maintainers can dispatch release-integrations.yml from main, select go, and provide a version without the v prefix. After validation succeeds and the protected release environment is approved, the workflow creates the scoped tag and GitHub Release and verifies the version through the public Go proxy.

Python and TypeScript release behavior is unchanged. The Go publication job alone receives contents: write.

Testing

• actionlint .github/workflows/release-integrations.yml
• git diff --check
• shell cases for Python, TypeScript, and Go release-tag routing
• ADK go.mod module-path validation
• source "$HOME/.gvm/scripts/gvm" && gvm use go1.25.2 && go test ./... in integrations/adk/go

Risks / follow-ups

Go versions are immutable once their scoped tag is visible. The publication step is idempotent only when an existing tag resolves to the same workflow commit; conflicting tags fail closed. Proxy verification happens after the GitHub Release is created and retries propagation failures.