Changelog

What shipped in fold, newest first. Every release carries its full notes on GitHub.

v1.15.0

An audit against the specification, and the breaking change it forced.

  • Every error code fold mints has changed, because the protocol reserved the range they were in.
  • The gateway can keep its own streams alive.
  • A routing header the caller sent stopped at the gateway.
  • The protocol-era transition is now instrumented and written down rather than assumed.
  • A retry that answered an upstream's question arrived looking like a first attempt.
  • A client had to be refused before it could learn which scopes it needed.
  • Every federated list went out with an invalid cache scope.
  • Policy and tenant selectors match on OAuth scopes, and a scope denial says what would fix it.
  • A caller could tell an upstream what protocol version, client identity, and capabilities it was talking to.
  • EMA advertised an authorization server that answered 404.
  • Nothing bounded what an upstream could return.
v1.14.0

Interactive apps survive the trip through the gateway.

  • An MCP App's interface belongs to the upstream that published it.
  • A client's rendering declaration now reaches the upstream.
  • The embedded console leads with what is wrong.
v1.13.0

An audit sink that authenticates no longer forces its token into the config.

  • A webhook audit sink can take its bearer token by reference.
v1.12.0

Governance in both directions, and one seam for judgement fold does not make itself.

  • Deny-by-default now applies to the reverse direction.
  • Policy learned depth: deny rules, argument constraints, and annotation gating.
  • fold notices when an upstream rewrites what it advertises.
  • The external decision hook, promised since v1.0, exists.
v1.12.1

Per-caller upstream credentials were only half-implemented; this is the other half.

  • An upstream whose credential comes from the caller now holds one session per principal.
  • /health stopped tearing down the upstreams it cannot probe.
  • The exchanged-token fetch gates are bounded.
v1.12.2

The images v1.12.1 should have published.

  • v1.12.1 shipped binaries and a chart but no container images.

Start where it hurts.

A single passthrough upstream in front of your most-used server is one config file away. Governance grows from there.

Get started