Package & Docker

The Go extension can produce release artifacts for Go projects, including Docker images. It owns the go ecosystem profile — the module-path and version rules, the shape of the workspace's registries.go entry, and the job that reports each published member — and publishes to the oci ecosystem the extension SDK owns.

Docker

When the docker publish channel is enabled, the Go extension assembles a digest-pinned gcr.io/distroless/static:nonroot image around the statically linked binary.

{
  "publish": ["docker"]
}

putnami build api --target linux/amd64
putnami publish api

Options include:

--docker-registry <registry> — an override; the declared target is registries.oci.publish in putnami.workspace.json
--docker-tag <tag>
--platform <platform>

The publisher pushes by digest and tags the version only. Channel tags are written by the release projection, never by the publisher, so a repeated publish of the same content is idempotent.

Registries

The Go endpoints come from the workspace's registries.go entry, overridable per project:

{
  "registries": {
    "go": {
      "origin": "https://go.example.com",
      "proxy": ["https://proxy.golang.org", "direct"]
    }
  }
}

origin is the vanity module server a publication uploads to and upgrade --channel resolves @v/<channel>.info on, per module — one channel carries a different version per module, so each module is pinned to its own. proxy is the ordered GOPROXY list and never leads with the origin. GO_REGISTRY_URL stays a one-off override. There is no options.publish.goRegistryUrl.

Archives and module publishing

Go packaging prepares platform archives and Go module source for release flows. A publication uploads the module zip to the origin, verifies the stored zip's digest, and reports the module as a published member of the release set; a 409 Conflict whose stored zip matches the local digest is a reuse, not a failure, which is what makes a repeated tagged publish idempotent.

Versions are derived from git for the version line the project belongs to; there is no --stable. Use Putnami build output as the source of truth for release artifacts rather than rebuilding manually in deployment scripts.