Skip to content

SILO Console 2.7.0

Choose a tag to compare

@github-actions github-actions released this 09 Nov 12:39
· 7 commits to main since this release

Ten UI languages with Arabic RTL, fixes to the usage worker, plain-HTTP and uploads, container CA and /tmp fixes, released mcli and silo-pkg, and updated API documentation.

English release notes · 中文发布说明 · Changes from 2.6.0

Changes

  • Languages: ten UI languages with saved preferences, locale-aware formatting and Arabic RTL. Changing language keeps unsaved inputs. The dictionaries are embedded and keep working offline once loaded. Brazilian Portuguese keeps the contribution and authorship from PR #83.
  • Container images: they now ship CA roots, which fixes HTTPS trust, and a /tmp directory, which fixes large multipart requests. The images still run as non-root. Read-only containers still need a writable /tmp mount.
  • Dependencies: released silo-pkg 3.16.0 and mcli 20261109, with exact release identities verified against the Go proxy, the checksum database and the committed module checksums.
  • API documentation: Swagger 0.36.7 and runtime/server-middleware 0.33.4. The array validators are regenerated, the customized server and configuration-import binding are preserved, the API documentation uses Redoc 3, and the /swagger.json route works.

Fixes found before release

  • Folder sizes over plain HTTP: "Calculate folder sizes" and the decryption-key copy now work over plain HTTP, for example at http://<ip>:9001. Previously both did nothing outside a secure context.
  • Usage-worker TLS: console usage-worker accepts --certs-dir. It trusts certs/CAs and Console's public.crt, and honors CONSOLE_MINIO_SERVER_TLS_SKIP_VERIFY for the SILO endpoint only. It neither creates the directory nor loads private.key.
  • Scan budget: CONSOLE_USAGE_SCAN_TIMEOUT limits listing time summed across slices, not time spent queued behind other buckets. Buckets left limited by the old accounting recover on their next retry.
  • Worker shutdown: scans interrupted by a worker shutdown are requeued with their checkpoint instead of being shown as failed. Bucket changes received before the worker stops are persisted.
  • Deleted buckets: a deleted bucket's totals are discarded on s3:BucketRemoved, including after a force delete, so a re-created bucket of the same name never shows them.
  • Busy scanner: without the usage database, Refresh retries an HTTP 429 from the scanner for about 30 seconds before reporting a bucket as failed.
  • Uploads: malformed or truncated multipart uploads return an error instead of causing a handler panic.
  • Arabic layout and task badge: in Arabic, the reveal button and unit selectors of password, URL, e-mail and number fields stay beside the text. The task-count badge is back in its corner position.

Upgrade note: stop older usage workers before starting 2.7.0 workers. Folder/bucket usage and the optional PostgreSQL worker first shipped in 2.6.0. Updating standalone Console does not update the Console embedded in a separately released SILO server.

Verification

Source: 4e91ae506e706ccdecb512b1d8b5ab4d9871d505.

Image: docker.io/pgsty/silo-console:v2.7.0 (Linux amd64/arm64), digest sha256:85aeb3ce802eb4aaae33503bcb665dc72c7544db037b5cda5ffae73b26719892.

The assets are:

  • six platform executables and bundles;
  • nine Linux packages;
  • the source archive and SPDX SBOMs;
  • the legal notices;
  • a signed SHA-256 manifest.

The tag workflow verifies the checksum and image signatures, the image SBOM attestations and the GitHub provenance. See the verification contract.