Skip to content

SILO Console 2.4.2 Released

mcli 20261018, minio-go v7.4.1, updated build tools and correct bucket-versioning errors.

Release: v2.4.2 · Source: ef2dd2c41d21.

Changes

  • Select published mcli 20261018, silo-pkg v3.14.2 and upstream minio-go v7.4.1. The SDK cleans up failed multipart uploads after cancellation, sends retention timestamps in UTC and preserves requested STS durations. Parallel GET and ComposeObject remain opt-in.
  • Preserve wrapped S3 errors from bucket-versioning operations and report InvalidBucketState explicitly when Object Lock prevents suspension. The Server’s protection remains unchanged.
  • Build with Go 1.27.2 and Node 24.22.0 LTS. Refresh Go x/* modules and targeted fixes in compress v1.20.3, msgp v1.6.5, etcd v3.7.2, fwd v1.2.1 and cpuid v2.4.1. Keep go-systemd v22.6.0 for NetBSD and tablewriter v0.0.5 for the existing MC API.
  • Use GoReleaser v2.18.3, golangci-lint v2.15.0 and govulncheck v1.9.0. Rebuild embedded assets as Console 2.4.2 and update the pinned source-build container.

Integration

Go consumers use v0.0.0-20261017112417-ef2dd2c41d21 because the retained module path has no /v2 suffix. An embedding Server must select both Console and MC replacements explicitly:

replace github.com/minio/console => github.com/pgsty/silo-console v0.0.0-20261017112417-ef2dd2c41d21
replace github.com/minio/mc => github.com/pgsty/mc v0.0.0-20261017101407-fa3b8bf72458

Console directly requires github.com/pgsty/silo-pkg/v3 v3.14.2. Existing password-permission migration rules remain in effect; see the migration guide. The go-jose v4.1.6 RSA JWK limit applies to Server OIDC code that imports it; go-jose and go-ldap are not linked into the standalone Console binary.

A standalone Console upgrade does not replace the Server binary or apply pending Server security and storage repairs. The current public Server remains 20260916; Server 20261018 has a signed tag and a verified Draft. The supported administrative target is SILO, with unmodified upstream MinIO compatibility on a best-effort basis.

Delivery and validation

Release binaries, archives, Linux packages and source are accompanied by checksums, SBOMs and signed provenance. The exact tagged commit passed the required CI matrix and vulnerability summaries, including permissions, SSO, replication, browser tests, source-image equivalence and reproducible packaging. Local acceptance also passed the full Go race suite and 251 frontend unit tests.

All 44 downloaded assets were verified. Six platform binaries, six bundles and nine Linux packages carry the expected source, dependency versions and legal material. The checksum manifest’s Sigstore signature and GitHub provenance were verified. The downloaded Console binary passed real API and browser sharing tests against the SILO 20261018 draft binary; Server remains unpublished.

The public docker.io/pgsty/silo-console:v2.4.2 tag selects this verified Linux amd64/arm64 image:

sha256:4cf47061e0d2f249df3c1cd2a939966ff3c69cc3cf7d10a7b1b39d5c110ae999

Release verification contract · Component matrix · Changes since v2.4.1.