SILO mcli release 20260913000000, packaged as 20260913000000.0.0 for Linux, macOS and Windows.
Fixes since the previous release
- Preserve mirror targets when historical source versions are deleted.
- Never turn an administrative restart dry run into a real restart; keep restart output reliable when stdout is not a terminal.
- Return transfer and SQL per-object failures as unsuccessful commands without misreporting them as usage errors.
- Preserve explicit checksums for empty uploads, honor pipe JSON/quiet flags, and accept on/off and enabled/disabled values in MC boolean environment variables.
- Keep CLI JSON output and cross-platform functional-test behavior consistent.
- Include silo-pkg policy fixes that preserve distinct Deny/NotResource clauses and string-condition values, and bound wildcard matching. Previously lost stored policy clauses still need to be restored from the original policy source.
Coordinated dependencies
Use released github.com/pgsty/silo-pkg/v3 v3.14.0 directly and upstream minio-go commit 60bd07042d49, including streaming Content-Type signing, RDMA TLS trust, listing checksums and restore-status fixes. Refresh the Go official x/* dependencies and the UBI certificate image, retain Go 1.27.1, and run govulncheck 1.8.0. The go-systemd 22.6.0 replacement remains the documented NetBSD build compatibility exception.
The package's password policy behavior has changed: admin:ChangeMyPassword and admin:CreateUser are separate capabilities. Policies that must preserve the previous combined restriction should deny both actions with the same scope and conditions. Use matching SILO Server and Console versions; see the migration guide.
The maintained integration target is pgsty/silo; upstream MinIO compatibility remains best effort.
Component status — 2026-09-13
pkg v3.14.0 and mcli 20260913 are published. Matching password-permission handling is merged in Server and Console, but their latest public releases remain Server 20260903 and Console v2.4.0 and do not contain that split. Installing the client alone does not change server-side authorization. Retain both CreateUser and ChangeMyPassword denies wherever the old combined restriction must survive an upgrade or rollback.
See the current component matrix, password-policy migration and website release notes.