[PureGo] Release v0.1.0 - #700
Merged
Merged
Conversation
Promote v0.1.0 notes into CHANGELOG.md, reset NEXT_CHANGELOG.md to the v0.2.0 template, guard the release workflow against a tag/version mismatch, and document the two-repo release flow in the README. Drop the deprecated FetchProtoDescriptor alias so the first release does not ship a deprecation for a name that was never public. Signed-off-by: Zlata Stefanovic <zlata.stefanovic@databricks.com>
Signed-off-by: Zlata Stefanovic <zlata.stefanovic@databricks.com>
teodordelibasic-db
approved these changes
Aug 7, 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
2 participants
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
Prepares the first release of the pure-Go SDK. PureGo ships as source rather than a built artifact — the
purego/v0.1.0tag is the release — so this PR only covers the changelog, docs, and release-workflow validation. Publishing is dispatched from a separate secure release environment, which invokesrelease-purego.ymlhere to build, vet, and test the module before scanningpurego/and creating the GitHub Release.v0.1.0notes intoCHANGELOG.mdand resetsNEXT_CHANGELOG.mdto av0.2.0template matching the C++ SDK's layout. The notes are rewritten as a first-release description of what the SDK does, rather than a log of in-development diffs, soBug FixesandAPI Changesare dropped: nothing shipped before v0.1.0 to fix or change.release-purego.ymlnow fails when apurego/v*tag disagrees with theversionconst inpurego/zerobus/sdk.go. That const feeds the gRPC user-agent and nothing else keeps the two in sync, so a mismatch would otherwise ship a release reporting the wrong version. It compares only theX.Y.Zcore, so prerelease tags still pass.SDK.FetchProtoDescriptoralias added in [PureGo] Remove UC descriptor cache #699. Since v0.1.0 is the first release, the old name was never public, and shipping it would bake a day-one deprecation into the v0 API that semver then requires a major bump to remove.purego/README.mdand removes a duplicated## Requirementssection.Test plan
release-purego.ymlagainst this branch as a pre-merge rehearsal — every step green (run 31195155878)build,vet,gofmt,go test -race, andCGO_ENABLED=0 go testclean for both the SDK and examples modulesstaticcheck ./...clean, confirming the alias removal left no dead codego mod tidyleaves no diff in either module, matching the workflow'sgit diff --exit-codestepsGITHUB_REF_NAME=purego/v0.1.0againstconst version = "0.1.0": passes, and fails on a deliberate mismatch## Release v0.1.0and pulls all three sections with no stray headings