Update Go publishing documentation with automatic publishing info #3422
+14
−7
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
Updates the Go publishing documentation to clarify that Go SDKs are automatically published to pkg.go.dev when repository requirements are met. This addresses customer confusion about Go SDK publishing (per internal Slack thread about Merge's Go SDK).
Key changes:
go.modand semantic version taghttps://pkg.go.dev/<go-module-path-in-go.mod>go.modhas a/v2suffix, the SDK publishes to a different URL<go-module-path-in-go.mod>for consistencyReview & Testing Checklist for Human
/v2module path versioning is technically accurate and clearly explains the issuehttps://pkg.go.dev/<go-module-path-in-go.mod>is correct and matches Go's actual behaviorNotes
Link to Devin run: https://app.devin.ai/sessions/1aee80761ff84568813b7a31fd67562e
Requested by: Fern Support (info@buildwithfern.com)