PGSTY SILO Blog

Console PR #83, contributed by Eduardo Andrade Machado, supplies Brazilian Portuguese. silo#277, opened by siyahkut, requests Turkish. These contributions led to a configurable ten-language UI. Status as of 2026-11-09: the ten-language UI, reviewed …

mcli 20261109 is released. Tag: RELEASE.2026-11-09T00-00-00Z; package version: 20261109000000.0.0; source: e1d4cc5abfe0. These notes describe changes since 20261026. This is a standalone mcli maintenance release. It does not replace the client …

Console 2.7.0 expands the administration interface to ten languages, fixes container HTTPS and temporary files, adopts the released mcli 20261109 and silo-pkg 3.16.0 and updates API documentation. It also fixes usage-worker TLS and scheduling, folder …

silo-pkg v3.16.0 is a source-only maintenance release of github.com/pgsty/silo-pkg/v3. It requires Go 1.27.3 and remains API-compatible with v3.15.2. Server, Console and mcli receive the changes only after adopting this version and rebuilding; their …

This record covers issue #284 and two regressions of the first native-restore safeguards for #281, described in Restored Copies: Expire the Copy, Not the Object. It was evaluated against main at 69fcf50cd and the integration branch for the next …

This record covers a defect found during local acceptance of the next release. It reproduces on the local integration of the next release and on 69fcf50cd. It has no GitHub issue yet. Status: fix approved by an adversarial review (with nits, all …

This record covers a defect found during local acceptance of the next release. It reproduces on 69fcf50cd and is inherited from upstream MinIO. It has no GitHub issue yet. Status: analyzed and reproduced. A fix was drafted, but an adversarial review …

Console 2.6.0 was published on 2026-11-05 (UTC+8), following 2.5.1. The GitHub release records source commit f8ab146695fd1df74e4b84128a286d552921bf00, release assets and verification evidence. This is a standalone Console release; Server’s embedded …

This record covers a lock-domain defect found during review of the restored-copy fix (Restored Copies: Expire the Copy, Not the Object), evaluated against main at 69fcf50cd. No issue has been filed yet. Status: fix approved by review and committed …

This record covers issue #281 and PR #282 by Denis Babchuk, evaluated against main at 69fcf50cd. The fix ships in the same maintainer integration PR as the multi-pool lifecycle fix (Multi-Pool Lifecycle Expiry, #278). That PR keeps the contributor …

This record covers issue #285 and PR #286 by Denis Babchuk, evaluated against main at 69fcf50cd and the PR head ed05d982a. Status: fix approved by review and committed locally. Tested together with the other fixes for the next release on one …

This record covers issue #278 and PR #279 by Denis Babchuk, evaluated against main at 69fcf50cd. The fix will ship through a maintainer integration PR that keeps the contributor commits unchanged and adds the maintainer follow-ups described below. …

This record covers the dry-run part of PR #280 by Jasper Bernhardt (@dihmandrake), evaluated against main at 69fcf50cd. The same PR also verifies an object’s drives concurrently during deep scans. That optimization is reviewed separately and is …

This record covers a defect found during review of the #278 fix (Multi-Pool Lifecycle Expiry). It was evaluated against main at 69fcf50cd and against the maintainer integration branch for #278 and #281, which is not yet published. Status: fix …

This record covers silo-console#72 (a quota set in the web Console shows as a dash in the bucket list) and silo-console#73 (numeric validation in the bucket-creation form). It is evaluated against the Console source before the fix, 3d264aea9, and the …

This record covers issue #259, reported by Henrik Feldt, evaluated against main at 69fcf50cd. The fix completes earlier, uncommitted maintainer work. It adds the Kafka call site, a handoff of records queued in a target that never started, and Kafka …

This record covers issue #265, the contributor change PR #266, and maintainer follow-up #276. The merged #264 and #267 are relevant predecessors. The review was updated against main after #276 on 2026-11-02. #266’s decommission commit is 19910230a, …

This record covers issue #263 and PR #264, updated against main at 0fc5a0b5, with the #264 merge recorded at 0cfca29c. The PR is three linked repairs, not three unrelated workarounds. Short answer The report is real. A free version is an internal …

This record covers issue #261 and PR #262, updated against main at 0fc5a0b5 after the #276 follow-up. The fix was merged through maintainer PR #267; #262 was the superseded duplicate. Short answer The report is real. A successful degraded overwrite …

This record reviews #261, #263, and #265, together with their fixes #262, #264, and #266. It also records the maintainer follow-up #276. It is a design and review record, not a release note. The review was updated against the post-#276 main branch on …