0.3.6

[achudnovskij]

Cuts a release so the GCS metadata-server auth fallback is actually consumable.

Why now

e844dff ("GCS: fall back to the metadata server when no key file is set") is on main but is in no published version. 0.3.5 was cut at 34deaae ("Expose read_segment") — the commit immediately before it. The crates.io index confirms 0.3.5 is the latest published version, so anything depending on wal-rus from the registry still gets the old "GOOGLE_APPLICATION_CREDENTIALS not set; metadata-server auth not yet supported" error.

wal-listener needs this to archive to GCS on GCP using the node's attached service account rather than a mounted key file.

Why a patch bump

e844dff touched only docs/DESIGN.md, docs/WALG_COMPAT.md and src/storage/gcs.rs. GcsConfig is unchanged and the new TokenSource enum is private, so there is no public API change and no Cargo.toml dependency change.

Contents

Cargo.toml + Cargo.lock only, matching the shape of previous release commits (92cdc4b "0.3.1", 49db691 "0.2.2").

Validation

cargo publish --dry-run passes: packages 148 files and the verify build compiles cleanly.

After merge

Publishing is manual — there is no publish workflow under .github/workflows, so someone with crates.io owner rights on wal-rus needs to run cargo publish.

That unblocks ClickHouse/wal-listener#23, which is pinned to 0.3.6 and cannot resolve its lockfile until this is on crates.io.

🤖 Generated with Claude Code