chore(sdk-go): release 0.2.0 - #1094
Merged
Merged
Conversation
The Go module has never carried a semantic version tag, so proxy.golang.org has only ever served v0.0.0-<date>-<commit>. Callers can use it, but cannot pin a release. 0.2.0 rather than 0.1.0 for the first tag: the code here is the same generation as the other four SDKs' 0.2.0 (35 commits since June, 26 of them feat), and starting at 0.1.0 would imply a maturity level two of them have already passed. DefaultUserAgent carries the SDK version and is sent on every request, so it is bumped in the same commit — it drifts silently if only the tag moves, which is exactly what the release doc warns about. No test hardcodes the string; they read the constant. go vet and go test pass.
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.
The Go module has never carried a semantic version tag, so
proxy.golang.orghas only ever servedv0.0.0-<date>-<commit>. Callers can use it, but cannot pin a release.0.2.0 rather than 0.1.0 for the first tag. The code here is the same generation as the other four SDKs' 0.2.0 — 35 commits since June, 26 of them
feat— and starting at 0.1.0 would imply a maturity level two of them have already passed.DefaultUserAgentcarries the SDK version and is sent on every request, so it is bumped in the same commit. It drifts silently if only the tag moves, which is exactly the failure the release doc added in #1088 warns about. No test hardcodes the string — they read the constant — andgo vetandgo testpass.After merge, the release is the tag itself:
sdk/go/v0.2.0, with the module's directory prefix. There is no publish workflow and none is possible; the proxy fetches on demand.Note this tag is immutable once the proxy serves it — deleting it does not take it back — so it goes on a commit already green on
main.