mcli 20261025

Released on 2026-10-25. The signed Git tag is RELEASE.2026-10-25T00-00-00Z, and the package version is 20261025000000.0.0. The downloads page provides platform archives, Linux packages, and Docker images. This client is part of the 20261025 maintenance batch.

Changes since 20261018

• Use Go 1.27.3 and silo-pkg v3.15.1, retaining shared policy evaluation improvements and existing authorization semantics. Refresh Prometheus, etcd, gRPC, JWX, JSON, and terminal dependencies. Go certificate-trust fixes and the release container root blocklist are covered in the maintenance announcement.
• Select upstream minio-go v7.4.2-0.20261020194015-ab93db7ba435. This is a pinned upstream commit after v7.4.1, not a formal v7.4.2 release. Truncated sequential and parallel multipart streams fail without completing a short object; a failed single-delete fallback produces one error result. The SDK also fixes ReadAt EOF and negative offsets, and read/seek bounds after Stat. Parallel SDK GET remains opt-in.
• Honor the optional region in persisted alias configuration. Selection follows MC_REGION, then AWS_REGION, then the alias; an unset region uses bucket-location discovery. Client caching distinguishes signing regions. This does not add an alias set --region flag.
• Return a nonzero exit status when admin info --json fails, while preserving its JSON error record. In 20261018, access denial could print status: error but still exit successfully.
• Package Windows amd64 and arm64 archives as ZIP. Linux and macOS retain tar.gz. Release checks verify formats, bundled documents, checksums, and binary source stamps.
• Clarify disabled server-update and SUBNET commands, SQL examples, and SILO help links. CI functional tests use the checksum-pinned SILO 20261018 release.

Upgrade considerations

The maintained release target is pgsty/silo. Unmodified upstream MinIO and other S3 services remain best-effort compatibility targets. This client update does not require a coordinated Server or Console upgrade.

Existing CLI configuration and MC_* variables remain supported. Compatibility selections retain go-systemd v22.6.0 for NetBSD, go-runewidth v0.0.29 for established terminal widths, and the tablewriter v0.0.5 API. Scripts that automate Windows downloads must select .zip for this version.

SIGINT during a CLI multipart upload exits with status 130 and can leave incomplete upload parts, as in 20261018; no completed object is exposed. Clean up the relevant prefix when needed:

mcli rm --incomplete --recursive --force ALIAS/BUCKET/PREFIX

A download interrupted in the middle of its body returns failure. Retry the command; the client must not report a truncated download as successful.

Acceptance and delivery

Local acceptance covers current SILO and its published 20261018 release over HTTP and trusted TLS; Go and Shell functional suites; SSE-S3, SSE-C, and a dedicated test KMS key; versioning, Object Lock, replication, IAM and STS; failed-copy source preservation, partial mirror failures, watch-mode history, SQL, and network fault recovery. Unit tests with the race detector, static checks, vulnerability scans, and all 262 visible command help pages pass. Six archives, six Linux packages, and both Linux container architectures pass local checks. All six package variants also pass installation of 20261018, upgrade to 20261025, rollback, and uninstallation while preserving client configuration. Logs and private fixtures remain outside the public repositories.

Local execution covers native macOS arm64 and Linux arm64, with Linux amd64 under emulation. Hosted CI also passes on native Windows amd64, macOS arm64, and Linux amd64. Windows arm64 and macOS amd64 remain cross-build-only targets in this acceptance. Server fixtures use one node and four data directories, not a production multi-node failure qualification. The filesystem-attribute test compares the pre-read snapshot and exercises Linux access-time updates caused by reading the upload source.

The release source is dcc78d506f94. The signed tag is published and remains fixed to this commit. GitHub’s Release workflow built the final artifacts from that tag.

Release gate passed for this exact commit: Go, Crosscompile, VulnCheck, and Test Release Pipeline all succeeded on push to main. Before building, the release-commit gate confirmed that the tagged commit was the tip of main and had all four required successful runs.

Published artifacts

The GitHub Release provides 19 files: six platform archives, six Linux packages, the archive checksum manifest, and six package checksum files. All 19 files were downloaded anonymously and matched their final SHA-256 digests. The six archive binaries carry the release commit above, and each package contains the corresponding Linux archive binary.

Both RPMs are signed with the PGSTY key 9592A7BC7A682E7333376E09E7935D8DB9BD8B20 (public key). All 11 GitHub build attestations were verified against the exact release tag, commit, filename, digest, and hosted Release workflow: six archives, the archive checksum manifest, two DEBs, and two APKs. RPM integrity is covered by its GPG signature because signing changes the package bytes after the build.

The Docker publication workflow published Docker Hub images for linux/amd64 and linux/arm64. Both were pulled back and run; their binaries match the public Linux archives, their OCI version and source labels match the release, and their legal files and certificate blocklist were checked. The version tag and latest resolve to the same multi-architecture digest:

docker.io/pgsty/mc:RELEASE.2026-10-25T00-00-00Z
sha256:770d5f14a70ecb88e0086d3a8061de726309bee986298fef06f09429fdd683cf

Use the version tag for an explicit release, or pin the index digest:

docker run --rm docker.io/pgsty/mc@sha256:770d5f14a70ecb88e0086d3a8061de726309bee986298fef06f09429fdd683cf --version

See downloads and installation for every platform and package format. Windows archives are ZIP; Linux and macOS archives remain tar.gz.