Release

Announcing Toise 0.17.1 — five fixes from field use

Released 2026-09-22 · written up 2026-09-30

0.17.1 gathers five fixes found in the first week of 0.17.0 in the field. Each makes an answer more dependable, so they ship as a patch rather than waiting for the next feature release.

Fixed

• MCP behind a buffering reverse proxy. The MCP listening stream is a long-lived GET. A proxy that buffers by default, as nginx does, could hold its headers back, and the client would hang on connect. The server now sends X-Accel-Buffering: no, so it works behind a proxy nobody configured for it.
• The relations filter accepts all three handle forms. A fingerprint in fromId or toId is now resolved like an id or an inline identity. A handle that cannot be resolved returns an empty result.
• entity_history points to earlier incarnations. History is keyed by the local id, so an entity re-minted after the resurrection window starts a new timeline. A timeline that opens on a creation now says so, and points to recent_changes with from and to. An index spanning incarnations would be a storage change and is left for later.
• recentChanges takes from and to on GraphQL. The MCP tool already did. Naming a window both ways is now an error rather than a silent choice.
• The resolution block names its quantity. It reports each producer's declared liveness interval, which is deliberately padded above the real cadence. It now says it is an upper bound, one that never under-states.

Upgrading

A drop-in patch for 0.17.0: no contract break, no data migration.

Get it

go install github.com/toise-dev/toise/cmd/toise-server@v0.17.1

Binaries for linux and darwin (amd64 / arm64) are on the release, each with a checksum, and the container image is on GHCR. See the 0.17.1 docs and the changelog.