Skip to content

Releases: restatedev/restate

v1.1.6

25 Dec 11:43
Compare
Choose a tag to compare

Restate 1.1.6

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.

IMPORTANT: If you upgraded a 1.0.x installation to version 1.1.1, please first upgrade to 1.1.2 or 1.1.3 before attempting a downgrade back to 1.0.2.

This version fixes an issue with the Kafka consumer where it could drop messages when starting to consume after the server starts, and an issue of growing memory usage over time due to oversized invoker in memory queues.

Full Changelog: v1.1.5...v1.1.6

v1.1.5

11 Dec 20:58
Compare
Choose a tag to compare

Restate 1.1.5

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.

IMPORTANT: If you upgraded a 1.0.x installation to version 1.1.1, please first upgrade to 1.1.2 or 1.1.3 before attempting a downgrade back to 1.0.2.

This release fixes a memory leak issue related to Prometheus Histograms - memory would grow unboundedly when metrics are not scraped

Full Changelog: v1.1.4...v1.1.5

v1.1.4

09 Dec 22:31
Compare
Choose a tag to compare

Restate 1.1.4

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.

IMPORTANT: If you upgraded a 1.0.x installation to version 1.1.1, please first upgrade to 1.1.2 or 1.1.3 before attempting a downgrade back to 1.0.2.

This release contains a small quality of life improvement from main while we work on the next minor release.

What's Changed

  • You may now provide Accept: application/json to the :9070/query endpoint to receive rows in JSON format.

Full Changelog: v1.1.3...v1.1.4

v1.1.3

19 Nov 19:06
Compare
Choose a tag to compare

Restate 1.1.3

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.

IMPORTANT: If you upgraded a 1.0.x installation to version 1.1.1, please first upgrade to 1.1.2 or 1.1.3 before attempting a downgrade back to 1.0.2.

This release contains various cherry picked fixes and quality of life improvements from main while we work on the next minor release.

What's Changed

  • Docker images now contain curl for easier health checking (#2006)
  • The admin role no longer assumes that the node svc port is 5122 (#2038)
  • Various otel improvements including exporting spans for ctx.run operations (#2291)
  • HTTP ingress path information including query string is now available as a special header (#2315)
  • Kafka ingress now supports talking to brokers over TLS, via a statically linked openssl library (#2292)

Full Changelog: v1.1.2...v1.1.3

v1.1.2

18 Sep 17:47
ed51cd8
Compare
Choose a tag to compare

Restate 1.1.2

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.

IMPORTANT: If you upgraded a 1.0.x installation to version 1.1.1, please first upgrade to 1.1.2 before attempting a downgrade back to 1.0.2.

This release contains an important compatibility update for anyone running Restate 1.1.1. Our versioning policy is to maintain rollback ability to the last minor version; Restate 1.1.1 broke this promise by shipping an upcoming feature called called log-server by default.

Please see the new Upgrading section on the Restate website for more information about version updates in general: https://docs.restate.dev/operate/upgrading.

If you are running Restate 1.0.x

We recommend that you upgrade directly to 1.1.2 (or the latest available patch release), and specifically to avoid 1.1.1.

If you are already running Restate 1.1.1

Please upgrade to 1.1.2 and delete the directory ${base_dir}/${node_name}/log-store to avoid issues with future upgrades. To avoid a crash on startup, please upgrade to 1.1.2 before attempting a downgrade back to 1.0.2.

What's Changed

Full Changelog: v1.1.1...v1.1.2

v1.1.1

16 Sep 15:38
bbe5bfb
Compare
Choose a tag to compare

Restate 1.1.1

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.

This is a bug fix release which corrects an issue making the sys_invocation_state introspection table inaccessible (#1961).

What's Changed

Full Changelog: v1.1.0...v1.1.1

v1.1.0

09 Sep 20:15
f8a1200
Compare
Choose a tag to compare

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

Read more

v1.0.2

21 Jun 09:52
604592b
Compare
Choose a tag to compare

What's Changed

  • We have identified a problem where Restate can get stuck after a restart. The problem can be solved by upgrading to this version w/o loss of data.

Details

Full Changelog: v1.0.1...v1.0.2

v1.0.1

11 Jun 18:19
17fd0df
Compare
Choose a tag to compare

What's Changed

  • Give user a tip if they run cloud login but they don't have an account by @jackkleeman in #1607

Full Changelog: v1.0.0...v1.0.1

Restate 1.0

07 Jun 10:01
Compare
Choose a tag to compare

We're happy to announce that Restate has reached the 1.0 milestone!

Storage compatibility

From this release onward, we guarantee storage compatibility when updating your Restate deployment. Check the versions documentation for more details.

From now on the SDK and Restate server releases are decoupled, meaning you will be able to run a service built with an old SDK version on newer server releases. More info on that to follow.

Workflow API

We have introduced a new API to simplify building workflows, check out the documentation: https://docs.restate.dev/develop/java/workflows

CLI

We have a bunch of new commands on the CLI to help you develop your application locally, check them out: https://docs.restate.dev/develop/local_dev

Metrics

The server now exports a lot of useful metrics to observe the system, check the documentation to configure them:https://docs.restate.dev/operate/monitoring/metrics

Full list of changes

Read more