Skip to content

RELEASE.2026-09-03T13-18-01Z

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 04 Sep 06:33
· 4 commits to main since this release
RELEASE.2026-09-03T13-18-01Z
This tag was signed with the committer’s verified signature.
Vonng Feng Ruohang
GPG key ID: E7935D8DB9BD8B20
Verified
Learn about vigilant mode.
9b11dc9
This commit was signed with the committer’s verified signature.
Vonng Feng Ruohang
GPG key ID: E7935D8DB9BD8B20
Verified
Learn about vigilant mode.

SILO 20260903 is a correctness and compatibility release built from 9b11dc9469e650815b775cb47b039610644f5da4. It is the complete supported release boundary after RELEASE.2026-08-06T00-00-00Z.

Highlights

  • Adds complete per-bucket CORS support, including site-replication convergence.
  • Serializes whole-record bucket metadata updates across configuration types, migration, import, adoption, and healing.
  • Aligns multipart and CopyObject checksum behavior, including server-computed part checksums and ChecksumType propagation.
  • Preserves SSE-C correctness for zero-byte reads, object attributes, copies, null-version rewrites, and key rotation.
  • Aligns explicit-version deletion and user/group status authorization with the requested operation.
  • Hardens MINIO_CONFIG_ENV_FILE parsing and legacy database-notification migration.
  • Moves to Go 1.27.1 and pins the maintained SILO dependency line.

Coordinated components

Verification

The exact release source passed Go CI, the complete cmd race suite, internal tests, lint, generated-file and compatibility guards, vulnerability scanning, cross-compilation, and the Test Release pipeline. Final functional acceptance used four Ubuntu 24.04 arm64 VMs with 16 XFS data disks and covered:

  • coordinated 20260806 → 20260903 upgrade, rollback, and second upgrade;
  • the mcli functional suite over TLS;
  • 1,004-object upload/download checksum comparison;
  • one-node outage, quorum loss, recovery, and single-drive reconstruction;
  • two-site replication, versions, CORS, tags, quota, ILM, Object Lock, IAM, delete markers, and offline catch-up.

Release archives and packages include SHA-256 manifests, SBOMs, and build provenance. RPMs carry the PGSTY GPG signature. Classic and distroless container images are published for linux/amd64 and linux/arm64.

The first container workflow stopped before pushing because the tagged Dockerfile retained stale mcli archive pins. The recovery workflow then resolved both pins from the immutable, attested mcli 20260903 checksum manifest and built from this Release's original Server archives. Run 33847571968 published and attested the final manifests:

  • classic release and latest: sha256:b616a0cf8cb281e7e6bb3c9b1fb53875b4016a2878223925541c18f82d6c5ca3
  • distroless release and rolling tag: sha256:2711cdc5bce0ada353a4871dcda60f48f46414fdd69a45c36c71f6b7ebe1aead

Upgrade notes

  • Upgrade every node in a distributed cluster in one coordinated maintenance operation.
  • Upgrade every site-replication member before creating or changing per-bucket CORS.
  • Review grants for s3:DeleteObjectVersion and the separate enable/disable admin actions.
  • Correct bare ARN prefixes before re-submitting policies.
  • Add connection strings to enabled legacy PostgreSQL/MySQL notification targets.
  • The signed tag's bundled Chart 7.0.2 retains a provisional T00-00-00Z image value. When rendering the chart from the tagged source archive, override image.tag=RELEASE.2026-09-03T13-18-01Z; the corrected current chart is on main at 4c164907f.

Known limitations, rollback guidance, and the full change ledger are documented in the complete release notes. Downloads and installation commands are on the SILO download page.

Assets 38
Loading