Embedding Console in a SILO server
September 3, 2026 ยท View on GitHub
SILO embeds this module (github.com/minio/console) as a Go dependency.
Console directly requires github.com/pgsty/silo-pkg/v3; that requirement is
inherited normally and needs no downstream replacement. Console has one
maintained replacement for the calendar-tagged pgsty/mc source. Go ignores
replacements declared by dependency modules, so an embedding server must copy
that one directive from the authoritative README block between the
silo-replacements markers.
Supported module graphs
| Module graph | Status |
|---|---|
The single pgsty/mc replacement from the README | Supported. downstream-embedder-compat builds a minimal embedder from the published block and checks both the replacement and the inherited pgsty/silo-pkg v3.13.2 requirement |
| No mc replacement | Best-effort compatibility probe, tested by the non-blocking upstream-pkg-compat job; this is not the released SILO graph and does not constrain maintained dependency versions |
The retired minio/pkg => silo-pkg or minio-go => silo-go replacements | Unsupported. silo-pkg v3.13.0 and later own github.com/pgsty/silo-pkg/v3, and minio-go now resolves upstream |
SILO keeps inexpensive source and wire compatibility where practical, but the
supported release graph is the coordinated PGSTY stack. A failure found only in
an unmodified upstream MinIO or mc graph is advisory: investigate and document
it, but do not downgrade silo-pkg or duplicate its APIs to make that graph
compile. minio-go is the explicit exception and resolves upstream by policy.
Keeping the block in sync
go run ./hack/replacements check(part ofmake verifiers) fails when the README block, the onego.moddirective, or the contract comment disagree.go run ./hack/replacements updateregenerates the README block after a dependency bump.go run ./hack/replacements readme-blockprints the published block; the CI embedder job feeds exactly that text into a scratch module.
Own-module-path migration
This Console line has completed the migration described by silo-pkg v3.13.0:
its source imports github.com/pgsty/silo-pkg/v3, and go.mod requires the
current v3.13.2 release directly. A SILO server adopting this Console release must make the same source
import migration. Keeping old github.com/minio/pkg/v3
imports while replacing that path with silo-pkg v3.13.0 or later produces
used for two different module paths. Update the embedding server's imports
and module graph when it adopts this Console release.