From a7bb03eb9b5d860ae80aa0090d2213dee218b059 Mon Sep 17 00:00:00 2001 From: "fern-api[bot]" <115122769+fern-api[bot]@users.noreply.github.com> Date: Sat, 31 Jan 2026 12:23:38 +0000 Subject: [PATCH 1/2] Update Go publishing documentation with automatic publishing info --- .../go/publishing-to-go-package-manager.mdx | 21 ++++++++++++------- 1 file changed, 14 insertions(+), 7 deletions(-) diff --git a/fern/products/sdks/overview/go/publishing-to-go-package-manager.mdx b/fern/products/sdks/overview/go/publishing-to-go-package-manager.mdx index a846597de..f3f1a8a5a 100644 --- a/fern/products/sdks/overview/go/publishing-to-go-package-manager.mdx +++ b/fern/products/sdks/overview/go/publishing-to-go-package-manager.mdx @@ -4,8 +4,7 @@ description: Learn how to publish your Fern-generated Go SDK to pkg.go.dev. Conf --- Publish your public-facing Fern Go SDK to -[pkg.go.dev](https://proxy.golang.org/). After following the steps on this page, -you'll have a versioned package published on pkg.go.dev. +[pkg.go.dev](https://proxy.golang.org/). Go SDKs are automatically published to the Go package manager when your repository meets the requirements below. No dedicated CI is needed for publishing. Versioned package published on Pkgsite @@ -17,8 +16,16 @@ you'll have a versioned package published on pkg.go.dev. To successfully publish your SDK as a Go module, your repository must have: * **Public** visibility * An [approved license](https://pkg.go.dev/license-policy) (e.g. [MIT](https://opensource.org/license/mit), [Apache](https://www.apache.org/licenses/LICENSE-2.0)) + * A valid Go module path in `go.mod` + * A semantic version tag pushed to the repository +Your SDK is published at `https://pkg.go.dev/`. + + + If your `go.mod` has a `/v2` (or higher) suffix in the module path, your SDK will publish to a different URL. For example, if your module path is `github.com/your-org/your-sdk/v2`, your SDK will be published at `https://pkg.go.dev/github.com/your-org/your-sdk/v2` instead of `https://pkg.go.dev/github.com/your-org/your-sdk`. + + ## Configure `generators.yml` @@ -64,16 +71,16 @@ you'll have a versioned package published on pkg.go.dev. - + - Navigate to `https://pkg.go.dev/github.com///` and send a request to index your package. In a few minutes, your new release should be published to [https://pkg.go.dev/](https://pkg.go.dev/)! + Once the semantic version tag is pushed, pkg.go.dev will automatically index your package. Navigate to `https://pkg.go.dev/` to verify your SDK is published. After releasing a new version, it may take a few minutes for pkg.go.dev - to index and display the update. You can also try checking to see if the Go + to index and display the update. You can also check if the Go proxy has indexed your module at - `https://proxy.golang.org/github.com///@v/list`. pkg.go.dev - indexing usually happens within 5-15 min of the proxy picking it up. + `https://proxy.golang.org//@v/list`. pkg.go.dev + indexing usually happens within 5-15 minutes of the proxy picking it up. For more information, see Go's documentation on [Adding a package](https://pkg.go.dev/about#adding-a-package). From 490db8a089bb2cb84afcb328cad58dd3f35248d9 Mon Sep 17 00:00:00 2001 From: Devin Logan Date: Wed, 4 Feb 2026 14:40:14 -0500 Subject: [PATCH 2/2] clarify structure --- .../go/publishing-to-go-package-manager.mdx | 20 +++++++------------ 1 file changed, 7 insertions(+), 13 deletions(-) diff --git a/fern/products/sdks/overview/go/publishing-to-go-package-manager.mdx b/fern/products/sdks/overview/go/publishing-to-go-package-manager.mdx index f3f1a8a5a..caf8162f4 100644 --- a/fern/products/sdks/overview/go/publishing-to-go-package-manager.mdx +++ b/fern/products/sdks/overview/go/publishing-to-go-package-manager.mdx @@ -4,7 +4,7 @@ description: Learn how to publish your Fern-generated Go SDK to pkg.go.dev. Conf --- Publish your public-facing Fern Go SDK to -[pkg.go.dev](https://proxy.golang.org/). Go SDKs are automatically published to the Go package manager when your repository meets the requirements below. No dedicated CI is needed for publishing. +[pkg.go.dev](https://pkg.go.dev/). Versioned package published on Pkgsite @@ -12,21 +12,15 @@ Publish your public-facing Fern Go SDK to - - To successfully publish your SDK as a Go module, your repository must have: - * **Public** visibility - * An [approved license](https://pkg.go.dev/license-policy) (e.g. [MIT](https://opensource.org/license/mit), [Apache](https://www.apache.org/licenses/LICENSE-2.0)) - * A valid Go module path in `go.mod` - * A semantic version tag pushed to the repository - +## Requirements -Your SDK is published at `https://pkg.go.dev/`. +Go SDKs are automatically published to [pkg.go.dev](https://pkg.go.dev/) when you push a semantic version tag to your repository and the repository meets the below requirements. No dedicated CI is needed. - - If your `go.mod` has a `/v2` (or higher) suffix in the module path, your SDK will publish to a different URL. For example, if your module path is `github.com/your-org/your-sdk/v2`, your SDK will be published at `https://pkg.go.dev/github.com/your-org/your-sdk/v2` instead of `https://pkg.go.dev/github.com/your-org/your-sdk`. - +Your repository must have: - +- Public visibility +- An [approved license](https://pkg.go.dev/license-policy) such as [MIT](https://opensource.org/license/mit) or [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0) +- A valid module path in `go.mod`, which determines your publish URL. For example, `github.com/your-org/your-sdk` publishes to `https://pkg.go.dev/github.com/your-org/your-sdk`. If your module path includes a major version suffix like `/v2`, your SDK publishes to that versioned URL instead (`https://pkg.go.dev/github.com/your-org/your-sdk/v2`). ## Configure `generators.yml`