v0.17.0

[0.17.0] - 2026-09-25

Fixed

• ravel-bench passes clippy -D warnings under --all-features
  (issue #1925). The read_path_accounting binary's Backend enum carried
  an unboxed S3Config in its S3 variant next to a data-less variant, so
  clippy::large_enum_variant failed cargo clippy --workspace --all-targets --all-features -- -D warnings. The build and tests were never affected;
  only the lint gate failed. The field is now boxed, with no change in
  behavior.

Changed

• The remaining MinIO identifiers are renamed to RustFS (issue #2008).
  The object store moved from MinIO to RustFS in 0.16.0 (#2002), which kept
  the old names; they now match. The RAVEL_MINIO_* variables that gate the
  S3 contract suite and the bench smoke tests are now RAVEL_RUSTFS_*, and
  the old names are no longer read, so anyone running those suites locally
  must rename them. The tests minio_contract and minio_ingest_read_smoke
  are now rustfs_contract and rustfs_ingest_read_smoke, and CI's checks
  that those tests really ran match the new names. sql_latency_bench
  reports the backend label "rustfs" instead of "minio", and
  read_path_accounting's Backend::Minio is Backend::RustFs. Test
  fixture hostnames and doc comments follow; where a comment stated how
  MinIO specifically behaved, it now makes a store-neutral statement
  instead.

What's Changed

• chore: rename the remaining MinIO identifiers to RustFS by @pmoust in #2009
• chore(release): prepare 0.17.0 by @pmoust in #2010

Full Changelog: v0.16.1...v0.17.0

Downloads

The attached binaries were extracted unmodified from the signed container
images this release published, so each one is byte-identical to the file inside
the image you can pull. They are glibc-dynamic, built against Debian 12
(the runtime image is gcr.io/distroless/cc-debian12), so they need glibc 2.36
or newer. On an older distribution, run the container image instead:

docker pull ghcr.io/nofireai/ravel-server:0.17.0

One binary per platform, named <binary>-<os>-<arch>:

• ravel-server-linux-amd64, ravel-server-linux-arm64
• ravel-cli-linux-amd64, ravel-cli-linux-arm64
• ravel-operator-linux-amd64, ravel-operator-linux-arm64
• ravel-ingest-router-linux-amd64, ravel-ingest-router-linux-arm64

Verifying the downloads

SHA256SUMS covers every attached binary and symbol archive. Check the files
you downloaded, then verify SHA256SUMS itself against the signature and
certificate beside it. The signature is keyless, bound to this release
workflow's identity, so there is no key to obtain:

sha256sum --check --ignore-missing SHA256SUMS

cosign verify-blob \
  --certificate SHA256SUMS.pem \
  --signature SHA256SUMS.sig \
  --certificate-identity 'https://github.com/NOFireAI/ravel/.github/workflows/publish-images.yml@refs/tags/v0.17.0' \
  --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
  SHA256SUMS

Debug symbols

The shipped binaries are stripped of debug info but keep their symbol table,
so a backtrace resolves function names with nothing extra installed. Line
numbers come from the matching symbols archive. Each binary records the
basename of its symbol file, so unpacking the archive next to the binary is
enough and no symbol-file step is needed:

tar -xzf ravel-debug-symbols-linux-amd64.tar.gz
gdb ./ravel-server-linux-amd64

gdb looks for ravel-server.debug in the same directory (and in
.debug/), which is the name inside the archive. Do not rename the extracted
.debug files.