Skip to content

v1.1.0

Compare
Choose a tag to compare
@pcholakov pcholakov released this 09 Sep 20:15
· 0 commits to 74d7363810a7f78dfe0845ae5347aa24957f4ab6 since this release
f8a1200

Restate 1.1.0

IMPORTANT for SDK-Typescript users: Only when upgrading from 1.0.x to 1.1.x you MUST rediscover all the existing deployments using restate dp register <address> --force. You don't need to update the SDK, nor change the code.

Notable changes:

  • Restate now sets the x-restate-invocation-id header when making service invocations to support load balancers implementing "sticky" routing
  • Improved forward- and backward-compatibility checks with data store on service startup
  • When discovering https service deployments, now both HTTP/1.1 and HTTP/2 are supported, with negotiation performed using ALPN. When discovering http deployments, HTTP/2 prior knowledge is assumed, but you can override it to use HTTP/1.1 by passing the --use-http1.1 flag to restate deployments register.
  • We now publish a Docker image restatedev/restate-cli containing the restate CLI tool (#1758)
  • Restate CLI and SQL interface now contain several additional fields to improve debugging your service invocations.

Notable bug fixes:

  • Service-to-service invocations will now correctly propagate headers
  • Tracing context header injection at the Restate ingress endpoint works as expected

Infrastructure updates:

  • Forward compatibility with the upcoming Service Invocation Protocol V2, enabling granular retry policies
  • Introduces the restatectl administrative tool which helps operators manage Restate cluster configuration
  • Foundational work on the Restate distributed log and data partitioning for upcoming distributed deployment support

What's Changed

New Contributors

Full Changelog: v1.0.2...v1.1.0