Skip to main content
2026-02-13
Restate Server v1.6.2

Restate v1.6.2

This patch release fixes a critical bug affecting lazy state users and includes several other bug fixes and improvements.

🐛 Critical Bug Fix: Lazy State Keys Encoding

If you are using lazy state (enableLazyState: true) and your handler calls ctx.stateKeys(), invocations could get stuck in a retry loop with a journal mismatch error (code 570) after suspending and resuming. The server was incorrectly storing GetLazyStateKeys commands as GetLazyState commands in the journal.Note: This only affects handlers with lazy state enabled that call ctx.stateKeys(). Handlers using eager state or only ctx.get(key) are not affected. The Java SDK is also not affected.After upgrading, new invocations work correctly. Existing stuck invocations have a corrupted journal and need to be resolved manually:
  1. Kill and re-invoke: restate invocations cancel --kill <INVOCATION_ID>
  2. Or apply an SDK-side fix (sdk-shared-core#60) that tolerates the mismatch during replay

🔧 Other Bug Fixes

  • SQL query predicate tolerance — Fixed a crash when DataFusion generated predicates with incorrect column indices for introspection table queries (#4389)
  • Fix clamp_max return value — Fixed incorrect reporting that a value was clamped when it was within the allowed range, which could cause spurious warnings during metadata schema processing

⚙️ Helm Chart: image.tag and image.digest

The version field in Helm chart values is now deprecated in favor of image.tag. A new image.digest field enables pinning images by SHA digest for reproducible deployments.
# New approach (replaces deprecated "version" field):
image:
  tag: "1.6.2"
# Or pin by digest:
image:
  digest: "sha256:abc123..."
Precedence: image.digest > image.tag > version. The version field continues to work for backward compatibility.

🖥️ Web UI Updates (v0.1.49)

  • Added support for displaying lazy state entries
  • Fixed display of lazy state keys entries
  • Minor UI improvements

📖 Full Release Notes →

Install

Pull the Docker images

```sh docker pull docker.restate.dev/restatedev/restate:1.6.2 docker pull docker.restate.dev/restatedev/restate-cli:1.6.2 ```

Install prebuilt binaries via Homebrew

```sh brew install restatedev/tap/restate-server brew install restatedev/tap/restate brew install restatedev/tap/restatectl ```

Install prebuilt binaries into your npm project

```sh npm install @restatedev/[email protected] npm install @restatedev/[email protected] npm install @restatedev/[email protected] ```

Download binary archives

View on GitHub
2026-02-10
Restate Server v1.6.1

Restate v1.6.1

This is a strongly recommended patch release for all v1.6.0 users, addressing critical stability and memory issues.

🔧 Critical Stability Fixes

Leadership Thrashing Resolved

In v1.6.0, RocksDB memory rebalancing could block the async runtime for 50–200ms, starving heartbeats and causing nodes to be falsely reported as down — leading to leadership loss and cluster instability. Memory rebalancing is now offloaded to background threads. If you experienced leadership thrashing on v1.6.0, this upgrade should resolve it.

Memory Leak in Networking Layer

Internal RPC callers that timed out could leave stale entries in the reply tracker, causing unbounded memory growth under sustained load. A periodic garbage collection mechanism now cleans these up automatically.

⚠️ Behavioral Change

The default worker.trim-delay-interval changed from 0s to 10m. This gives follower replicas time to catch up before log segments are trimmed, reducing unnecessary re-snapshotting. To restore the old behavior, set worker.trim-delay-interval = "0s" in your config.

🧠 Memory Improvements

  • Eliminated high-water-mark buffer retention — Per-invocation protocol encoders no longer retain buffers sized to the largest message ever encoded, reducing memory overhead for clusters with many concurrent long-lived invocations.
  • Lazy journal & state reading during replay — Journal entries and state are now read on demand from RocksDB instead of being fully materialized upfront, reducing peak memory during replay of invocations with large journals or state.

✨ New Features

  • OTEL_RESOURCE_ATTRIBUTES support — Attach deployment-specific metadata (environment, region, pod name) to all exported traces via the standard environment variable 🔍
  • services column in sys_deployment — Query which services belong to which deployment directly via SQL 🗃️
  • Weekly Docker image security refreshes — Images are now automatically rebuilt weekly with the latest OS security patches. Use date-suffixed tags (e.g., 1.6.1-20260210) to pin specific builds 🐳

⚡ Performance Improvements

  • More efficient invocation cleanup scans
  • SQL query push-down filters for faster introspection queries on large tables
  • Faster ID encoding (Base62)

🖥️ Web UI Updates (v0.1.46)

  • Invocation duration column in the list view
  • Paused invocations now show their error/reason directly
  • Multiple bug fixes for journal ordering, transient error display, and state page refresh

🔒 Security

  • Patched DoS vulnerability in time crate (RUSTSEC-2026-0009)
  • Updated bytes crate to address security advisory

📖 Full Release Notes →

Install

Pull the Docker images

docker pull docker.restate.dev/restatedev/restate:1.6.1
docker pull docker.restate.dev/restatedev/restate-cli:1.6.1

Install prebuilt binaries via Homebrew

brew install restatedev/tap/restate-server
brew install restatedev/tap/restate
brew install restatedev/tap/restatectl

Install prebuilt binaries into your npm project

npm install @restatedev/[email protected]
npm install @restatedev/[email protected]
npm install @restatedev/[email protected]

Download binary archives

View on GitHub
2026-01-30
Restate Server v1.6.0

Restate v1.6.0 🎉

✨ Release Highlights

⏸️ Pause and Resume for Invocations

Gain explicit control over invocation execution! You can now manually pause running invocations and resume them later — even on a different deployment. Invocations now pause by default when max retries are exhausted, giving you time to investigate issues before deciding to resume, restart, or kill.
# Pause a stuck invocation
restate invocations pause <invocation_id>

# Resume when ready (optionally on a different deployment)
restate invocations resume <invocation_id> --deployment latest

🔄 Restart Invocation from Journal Prefix

Preserve your expensive work when restarting invocations! Keep completed calls, sleeps, and side effects instead of re-executing everything from the beginning. Perfect for recovering from issues without losing progress.

🚀 Deployment Registration Improvements

Safer and more robust deployment workflows:
  • Idempotent registration — re-registering the same deployment returns HTTP 200 ✅
  • Default force=false — better protection against accidental overwrites
  • New breaking flag — allow breaking changes while still protecting against accidents
  • Update Deployment API — fix tokens or rotate credentials without re-deploying

🧠 Memory Management Improvements

Better performance with a lower memory footprint out of the box:
  • Automatic partition store memory balancing across all active partitions
  • Optimized RocksDB defaults (2 GiB total, 85% memtables)
  • Reduced query engine memory usage

🔍 Error Events Enabled by Default

Better observability for debugging invocations! When invocations encounter transient failures, Restate now automatically records detailed error information in the journal — visible in the UI invocation timeline and queryable via SQL. See exactly why invocations are failing during retries, including error codes, messages, stacktraces, and the related command that caused the failure.

☁️ Expanded Cloud Provider Support

Simpler cloud deployments with native integrations for AWS, Azure, and GCP:
  • Azure Blob Storage & Google Cloud Storage snapshots — store partition snapshots natively in Azure (az://) or GCS (gs://), in addition to Amazon S3

🆕 More New Features

  • restate up command — spin up a local Restate server for development with a single command! 🚀
  • Kafka SASL OAUTHBEARER/OIDC — connect to Confluent Cloud, Amazon MSK, and Azure Event Hubs 🔐
  • Unix Domain Sockets — the server now listens on both TCP and Unix sockets by default 🔌
  • Batch invocation operations — operate on hundreds of invocations at once with progress bars 📊

⚠️ Important Breaking Changes

Deprecated SDK Versions Now Rejected

New invocations will be rejected for services using deprecated SDK versions:
  • Java/Kotlin < 2.0
  • TypeScript <= 1.4
  • Go < 0.16
  • Python < 0.6
  • Rust < 0.4
Existing in-flight invocations continue normally. See migration guidance →

Retry Policy Configuration Migration

The deprecated worker.invoker.retry-policy has been removed. Migrate to invocation.default-retry-policy. Invocations now pause by default when max attempts are reached.

Helm Chart Resource Limits Increased

Default resource limits increased to 8Gi memory / 4 CPU. A default value of 3Gi is now specified for RESTATE_ROCKSDB_TOTAL_MEMORY_SIZE. Check your cluster has sufficient resources before upgrading.

restate cloud env tunnel changes

The Cloud Tunnel now operates as a reverse proxy, instead of routing to a specific local port:
restate cloud env tunnel --tunnel-name my-tunnel
restate dp register --tunnel-name my-tunnel http://localhost:9080
# you can even proxy to external urls
restate dp register --tunnel-name my-tunnel https://my-worker.workers.dev

📖 Full Release Notes →

Install

Pull the Docker images

docker pull docker.restate.dev/restatedev/restate:1.6.0
docker pull docker.restate.dev/restatedev/restate-cli:1.6.0

Install prebuilt binaries via Homebrew

brew install restatedev/tap/restate-server
brew install restatedev/tap/restate
brew install restatedev/tap/restatectl

Install prebuilt binaries into your npm project

npm install @restatedev/[email protected]
npm install @restatedev/[email protected]
npm install @restatedev/[email protected]

Download binary archives

View on GitHub
2025-12-11
Restate Server v1.5.6

Restate v1.5.6

Install

Pull the Docker images

docker pull docker.restate.dev/restatedev/restate:1.5.6
docker pull docker.restate.dev/restatedev/restate-cli:1.5.6

Install prebuilt binaries via Homebrew

brew install restatedev/tap/restate-server
brew install restatedev/tap/restate
brew install restatedev/tap/restatectl

Install prebuilt binaries into your npm project

npm install @restatedev/[email protected]
npm install @restatedev/[email protected]
npm install @restatedev/[email protected]

Download binary archives

What’s changed:

View on GitHub
2025-11-27
Restate Server v1.5.5

Restate v1.5.5

Install

Pull the Docker images

docker pull docker.restate.dev/restatedev/restate:1.5.5
docker pull docker.restate.dev/restatedev/restate-cli:1.5.5

Install prebuilt binaries via Homebrew

brew install restatedev/tap/restate-server
brew install restatedev/tap/restate
brew install restatedev/tap/restatectl

Install prebuilt binaries into your npm project

npm install @restatedev/[email protected]
npm install @restatedev/[email protected]
npm install @restatedev/[email protected]

Download binary archives

What’s Changed

View on GitHub
2025-11-25
Restate Server v1.5.4

Restate v1.5.4

Install

Pull the Docker images

docker pull docker.restate.dev/restatedev/restate:1.5.4
docker pull docker.restate.dev/restatedev/restate-cli:1.5.4

Install prebuilt binaries via Homebrew

brew install restatedev/tap/restate-server
brew install restatedev/tap/restate
brew install restatedev/tap/restatectl

Install prebuilt binaries into your npm project

npm install @restatedev/[email protected]
npm install @restatedev/[email protected]
npm install @restatedev/[email protected]

Download binary archives

What’s Changed

View on GitHub
2025-10-21
Restate Server v1.5.3

Restate v1.5.3

Install

Pull the Docker images

docker pull docker.restate.dev/restatedev/restate:1.5.3
docker pull docker.restate.dev/restatedev/restate-cli:1.5.3

Install prebuilt binaries via Homebrew

brew install restatedev/tap/restate-server
brew install restatedev/tap/restate
brew install restatedev/tap/restatectl

Install prebuilt binaries into your npm project

npm install @restatedev/[email protected]
npm install @restatedev/[email protected]
npm install @restatedev/[email protected]

Download binary archives

What’s Changed

View on GitHub
2025-10-08
Restate Server v1.5.2

Restate v1.5.2

Install

Pull the Docker images

docker pull docker.restate.dev/restatedev/restate:1.5.2
docker pull docker.restate.dev/restatedev/restate-cli:1.5.2

Install prebuilt binaries via Homebrew

brew install restatedev/tap/restate-server
brew install restatedev/tap/restate
brew install restatedev/tap/restatectl

Install prebuilt binaries into your npm project

npm install @restatedev/[email protected]
npm install @restatedev/[email protected]
npm install @restatedev/[email protected]

Download binary archives

What’s Changed

View on GitHub
2025-10-01
Restate Server v1.5.1

Restate v1.5.1

Install

Pull the Docker images

docker pull docker.restate.dev/restatedev/restate:1.5.1
docker pull docker.restate.dev/restatedev/restate-cli:1.5.1

Install prebuilt binaries via Homebrew

brew install restatedev/tap/restate-server
brew install restatedev/tap/restate
brew install restatedev/tap/restatectl

Install prebuilt binaries into your npm project

npm install @restatedev/[email protected]
npm install @restatedev/[email protected]
npm install @restatedev/[email protected]

Download binary archives

What’s Changed

View on GitHub
2025-09-16
Restate Server v1.5.0

v1.5.0 Release notes

[NOTICE] http-ingress server role

In v1.4.x you might have seen this warning:
💡 !!! This node has a worker role and no explicit http-ingress role. http-ingress will be started anyway in this version. In v1.5, running ingress will require the role http-ingress to be set.
It’s now the time to ask you to add http-ingress to the list of roles you pass down to restate-server. This is only required if you use a configuration file, or if you pass roles as an argument restate-server --roles .Starting from Restate v1.5.0, HTTP Ingress is started on nodes with http-ingress role. In previous version, http ingress was part of the worker role. The separation of roles enables users to scale-out ingress nodes independently from log-servers or worker .You don’t need to change anything if you have not set the roles explicitly before.

Invocation progress retained by default

You’ll be able to inspect the invocation progress after the invocation completed for 24 hours, without additional configuration.As in the previous release, you can tune this configuration using the journal retention knob on a service or handler basis. Check out the docs for service configuration. You can also set up a maximum journal retention value for your cluster using the configuration option max-journal-retention, by default disabled. This can be used in production setups to clamp the journal retention advertised by service configurations to an acceptable value of your choice.

New invocation retry policy

Based on your feedback, we have revamped the invocation retry policy experience. Restate v1.5.0 includes few new bits:
  • The new configuration option default-retry-policy, which will replace worker.invoker.retry-policy in the upcoming releases.
  • The new retry policy will now, by default, pause an invocation when max-attempts is reached. This avoids unnecessary retries, that incur in wasteful costs for FaaS users. You can inspect paused invocations, check the failure reason, and resume them simply clicking the Resume button in the UI (or CLI).
  • You can now override the invocation retry policy on a service/handler basis, similar to other configuration options. Check out the docs for service configuration.
To opt-in the new invocation retry policy experience, you need to set the new default-retry-policy in the restate-server configuration, e.g.:
[default-retry-policy]
initial-interval = "10s"
max-attempts = 100
In order to obtain the old behavior where invocations get killed once they reach the maximum attempts, you have to configure:
[default-retry-policy]
initial-interval = "10s"
max-attempts = 100
on-max-attempts = "kill"
When opting-in default-retry-policy, you can’t rollback to Restate v1.4.x, therefore, it’s safe to use this configuration only after upgrading all cluster nodes to v1.5.0.

SQL query engine performance

The SQL introspection query engine that powers the UI and CLI has received a major performance boost. Queries now run 5x to 20x faster making the UI/CLI experience snappier in high data volume environments.We also solved several cases where queries led to the exhaustion of query engine memory.For best results make sure you upgrade the CLI to the latest version along with your restate server.

Lambda compression

Restate server will now compress requests before sending them to AWS Lambda, when approaching the invocation payload limit. This allows for larger replays without hitting the PAYLOAD_TOO_LARGE error from Lambda.Currently, this feature is only supported with services built with sdk-typescript ≥ 1.9, and doesn’t require any explicit activation.

Restart as new

You can now restart failed or succeeded invocations from the UI (or CLI) reusing the same request input. When restarting, a new invocation with a new invocation ID will be created.This is a useful shortcut when you need to re-process the same request, without having the input at hand. No need to build your own dead letter queue logic anymore, just restart the failed invocations when you need to.

Retry now

Sometimes a back-off retry timer might be way too long, and you need to retry an invocation immediately. To do that, you can now simply click Retry now for an invocation in the UI.

Access log

Ingress and Admin API now have an access log feature, that logs all accesses to the APIs.To enable it, enable the log filters restate_ingress_http::api and restate_admin::api. For example, to enable the default INFO logging plus the access log of ingress and Admin API: RUST_LOG=restate_admin::api,restate_ingress_http::api,info

Changes to service configuration

Starting from Restate v1.5.0, changes to the service configuration made through UI, CLI or Admin API will apply until a new revision of that service is registered. Check out the docs for service configuration for more details.

Deprecated old SDKs

In Restate v1.5.0 you won’t be able to register service deployments that use the following SDK versions:
  • Java SDK < 2.0
  • Typescript SDK < 1.5
  • Python SDK < 0.6
  • Go SDK < 0.16
  • Rust SDK < 0.4
In-flight invocations will continue to work fine. We strongly suggest to update to the latest SDKs to profit from all the new features!

Install

Pull the Docker images

docker pull docker.restate.dev/restatedev/restate:1.5.0
docker pull docker.restate.dev/restatedev/restate-cli:1.5.0

Install prebuilt binaries via Homebrew

brew install restatedev/tap/restate-server
brew install restatedev/tap/restate
brew install restatedev/tap/restatectl

Install prebuilt binaries into your npm project

npm install @restatedev/[email protected]
npm install @restatedev/[email protected]
npm install @restatedev/[email protected]

Download binary archives

View on GitHub
2025-08-08
Restate Server v1.4.4

Restate v1.4.4

Install

Pull the Docker images

docker pull docker.restate.dev/restatedev/restate:1.4.4
docker pull docker.restate.dev/restatedev/restate-cli:1.4.4

Install prebuilt binaries via Homebrew

brew install restatedev/tap/restate-server
brew install restatedev/tap/restate
brew install restatedev/tap/restatectl

Install prebuilt binaries into your npm project

npm install @restatedev/[email protected]
npm install @restatedev/[email protected]
npm install @restatedev/[email protected]

Download binary archives

What’s Changed

Stability, Consistency & Data Integrity

  • Metadata Server Reliability: The replicated metadata server now ensures the latest NodesConfiguration is effectively tracked and used.
  • Bifrost Log Chain Resilience: Multiple enhancements to Bifrost components improve log chain consistency:
    • Eager chain sealing on find_tail when consistency is required.
    • Clear diagnostics on why chain markers are created.
    • Automatic sealing of read streams upon detection of partial seals.
    • Watchdog-driven management of LogChainExtender, plus unified chain operations via LogChainWriter and a configurable read batch limit.
  • Crash Safety: On panic, RocksDB’s WAL is guaranteed to be flushed, minimizing data loss risk.

Operational Hygiene & Reliability

  • Worker Task Cleanup: Streamlined task management removes stale processes and avoids unintended pinning of the partition store manager.
  • Snapshotting Improvements: Partition snapshot tasks are now smoother and more efficient.
  • Ingress Runtime Simplification: Removed dedicated ingress runtime to simplify deployment architecture.
  • Histogram & Metrics Tweaks:
    • Idle histogram timeouts disabled by default.
    • Configuration option for histogram timeout removed entirely.
    • Reduced metrics cardinality, benchmarked to debug builds only.
  • Test Stability: Auto-improvement features are disabled in replicated-loglet integration tests for more predictable outcomes.
  • Fix in Cluster State Logic: Corrected an issue where failing-over nodes could be falsely marked as alive.
  • Config Reload Enhancements: Live updates after config reload now correctly reflect in applied DB settings.

Ecosystem & Interface Updates

  • Observability Improvements: The object store now emits richer telemetry, helping operators better monitor key storage operations.
  • CLI Enhancements: Added “single-address mode” to restatectl for more flexible node targeting.
  • Admin/API UX Tweaks:
    • Workflow retention now correctly reflects in Admin API.
    • Added completion_retention and journal_retention fields to the SQL interface.
  • Restate UI Refresh: Updated UI to versions v0.0.93 and v0.0.94 for interface polish. Plus, users are now prompted to choose where example assets are downloaded.
  • SDK Telemetry: The Admin API now captures and reports information about used SDKs.

New Contributors

View on GitHub
2025-07-29
Restate Server v1.4.3

🎉 Restate v1.4.3: Multi-region Restate cluster

We are pleased to announce the release of Restate v1.4.3! This release brings several improvements, new features, bug fixes, and enhancements across the platform. 🚀

✨ Highlights

🛠️ CLI/Tool Enhancements

  • 🔧 Shell Completions for restatectl and restate CLI: Both CLI tools now support shell completions for bash, zsh, fish, and PowerShell, with automatic shell detection and installation commands. This significantly improves the developer experience when working with Restate from the command line! 💻
  • 📍 Location Display in restatectl node ls: The restatectl node ls command now includes location information in its output, providing better visibility into node placement.

📊 Observability & Tracing

  • 🔗 OTLP+HTTP Support: Added support for OTLP+HTTP in the tracing endpoint, expanding observability integration options.
  • 🎨 Updated Web UI: Restate UI has been updated to v0.0.92 with various improvements.

⛵ Helm Chart Improvements

  • 🔄 Flexible Environment Variable Configuration: The Helm chart now allows avoiding setting nodeName or advertisedAddress, enabling more flexible environment variable management and preventing duplicate env var issues that can cause problems with Helm.
  • ⚙️ Custom Command and Args Support: Added support for specifying custom command and arguments in the Helm chart, allowing advanced entrypoint scripting (e.g., fetching availability zones from AWS). ☁️
  • 📦 Stateful Set Fix: The version is no longer set in stateful sets, resolving potential upgrade issues.

🌊 Bifrost & Log Management

  • 🔐 Experimental Chain Sealing: Added experimental support for chain sealing markers, allowing log chains to be sealed with a special marker in metadata without requiring reconfiguration. This feature includes:
    • A new restatectl log seal &lt;LOG-IDs&gt; command for manual chain sealing 🔨
    • Support for empty logs and advanced snapshot/reconfiguration scenarios 📸
    • Foundation for seamless cluster restoration with initial LSN offsets 🔄
  • ✂️ Experimental Partition-driven Log Trimming: Introduced experimental feature worker.experimental-partition-driven-log-trimming that replaces cluster-controller-driven trimming with partition leader-based durability tracking.

💾 Storage & Partition Management

  • 🔒 Fine-grained Partition Store Locking: Implemented a new locking model for partition stores with improved ownership patterns and lifecycle management.
  • 📈 Durable LSN Tracking Improvements: Enhanced durable LSN loading from persistent storage on partition store open, with new watch mechanisms for better state tracking.
  • 🗃️ RocksDB Management Refactoring: Improved RocksDB manager with better ownership model, background operation handling, and cleaner shutdown procedures.

🏗️ Metadata & Cluster Management

  • 🤝 Metadata Server Auto-join Control: Added MetadataServerOptions::auto_join to control whether nodes automatically join the metadata cluster on startup.
  • 🔄 Improved Node Removal Handling: Enhanced handling of node removal scenarios, including better reconfiguration completion when all current workers are disabled.

🐛 Bug Fixes

  • ⚡ Scheduler Reconfiguration Bug: Fixed a bug in Scheduler::complete_reconfiguration where wrong version comparison could lead to premature reconfiguration completion.
  • ✅ Reconfiguration Logic Fixes: Corrected Scheduler::requires_reconfiguration checks that could cause false positives.
  • 🔄 Service Type Change Handling: Fixed issues when overwriting services and changing their type.
  • 🌐 HTTP Protocol Detection: Improved error detection when mixing HTTP/1.1 and HTTP/2 protocols.
  • 🔍 Loglet Index Management: Fixed bugs in lookup index management for replicated loglets.
  • 📝 Sequencer Write Availability: Fixed issues where SequencerAppender can now reconfigure logs that become write unavailable due to read-only node marking.

📈 Upgrade Notes

You can safely upgrade from Restate x.y to x.(y+1) releases without manual data migration, as Restate performs automatic data migration for you. 🔄For detailed technical information about the changes, refer to the commit history in the release: https://github.com/restatedev/restate/compare/v1.4.2…v1.4.3
This release represents significant improvements in developer experience, operational capabilities, and system reliability! 💪 The new shell completions and Helm chart enhancements make Restate easier to deploy and manage, while the experimental features pave the way for advanced log management capabilities. 🎯

Install

Pull the Docker images

docker pull docker.restate.dev/restatedev/restate:1.4.3
docker pull docker.restate.dev/restatedev/restate-cli:1.4.3

Install prebuilt binaries via Homebrew

brew install restatedev/tap/restate-server
brew install restatedev/tap/restate
brew install restatedev/tap/restatectl

Install prebuilt binaries into your npm project

npm install @restatedev/[email protected]
npm install @restatedev/[email protected]
npm install @restatedev/[email protected]

Download binary archives

View on GitHub
2025-07-07
Restate Server v1.4.2

Restate v1.4.2

Install

Pull the Docker images

docker pull docker.restate.dev/restatedev/restate:1.4.2
docker pull docker.restate.dev/restatedev/restate-cli:1.4.2

Install prebuilt binaries via Homebrew

brew install restatedev/tap/restate-server
brew install restatedev/tap/restate
brew install restatedev/tap/restatectl

Install prebuilt binaries into your npm project

npm install @restatedev/[email protected]
npm install @restatedev/[email protected]
npm install @restatedev/[email protected]

Download binary archives

View on GitHub
2025-06-25
Restate Server v1.4.1

Restate v1.4.1

What’s Changed

Install

Pull the Docker images

docker pull docker.restate.dev/restatedev/restate:1.4.1
docker pull docker.restate.dev/restatedev/restate-cli:1.4.1

Install prebuilt binaries via Homebrew

brew install restatedev/tap/restate-server
brew install restatedev/tap/restate
brew install restatedev/tap/restatectl

Install prebuilt binaries into your npm project

npm install @restatedev/[email protected]
npm install @restatedev/[email protected]
npm install @restatedev/[email protected]

Download binary archives

View on GitHub
2025-06-23
Restate Server v1.4.0

Restate v1.4.0

[NOTICE] Expect a short period of leader unavailability during rolling upgrades from v1.3.2 to v1.4.0 due to changes in cluster controller and gossip protocol. The availability is transient and the cluster will quickly fix all partition leaders once all cluster nodes have been upgraded.

Release Highlights

  • Restate clusters will automatically perform partition rebalancing across configured nodes. This delivers even space and compute utilization across the board.
  • A new gossip-based failure detector and partition leader placement sub-systems which deliver up to 10x faster detection of network partitions or node failures. Gossip is also used to disseminate partition leadership state for faster reaction to partition reconfigurations.
  • The Replicated Loglet is the default in v1.4. Existing loglets backed by the Local Loglet provider will be automatically migrated on first run. Replicated Loglet delivers better performance even for single-node deployments and is the recommended provider in all cases. The Local Loglet continues to be available and automatic migration will not be performed if it is explicitly configured as the default provider. Downgrading to Restate v1.3 is safe regardless of which loglet provider is used.
  • The previously deprecated local metadata backend for single-node deployments is removed in v1.4.0. The default is the replicated metadata server, nodes will perform automatic migration on start.
  • Restate server role http-ingress is enabled by default, new setups will automatically have this role turned on.
  • Query engine optimizations and fixes that improve responsiveness and system reliability under severe load and slow storage backends.
  • Default invoker concurrent invocation node defaults to 1000 instead of 100.
  • Zstd compression is promoted to default for the message fabric in restate clusters.
  • Partition Processors now track the locally-persisted LSN automatically. This is now reported by restatectl as Durable LSN (from Persisted LSN). The configuration properties worker.storage.persist-lsn-interval and worker.storage.persist-lsn-threshold are no longer required and will be ignored. If you previously used these to tune single-node log trimming, you can safely remove them.
  • admin.query-engine.pgsql-bind-address has been deprecated and its default value was set to None (https://github.com/restatedev/restate/issues/3088)
  • Various previously deprecated configuration properties have been removed (admin.log-trim-threshold , metadata-store-client.address)

Install

Pull the Docker images

docker pull docker.restate.dev/restatedev/restate:1.4.0
docker pull docker.restate.dev/restatedev/restate-cli:1.4.0

Install prebuilt binaries via Homebrew

brew install restatedev/tap/restate-server
brew install restatedev/tap/restate
brew install restatedev/tap/restatectl

Install prebuilt binaries into your npm project

npm install @restatedev/[email protected]
npm install @restatedev/[email protected]
npm install @restatedev/[email protected]

Download binary archives

What’s Changed

New Contributors

View on GitHub
2025-04-18
Restate Server v1.3.2

Restate v1.3.2

Install

Pull the Docker images

docker pull docker.restate.dev/restatedev/restate:1.3.2
docker pull docker.restate.dev/restatedev/restate-cli:1.3.2

Install prebuilt binaries via Homebrew

brew install restatedev/tap/restate-server
brew install restatedev/tap/restate
brew install restatedev/tap/restatectl

Install prebuilt binaries into your npm project

npm install @restatedev/[email protected]
npm install @restatedev/[email protected]
npm install @restatedev/[email protected]

Download binary archives

View on GitHub
2025-04-16
Restate Server v1.2.3

Restate v1.2.3

Install

Pull the Docker images

docker pull docker.restate.dev/restatedev/restate:1.2.3
docker pull docker.restate.dev/restatedev/restate-cli:1.2.3

Install prebuilt binaries via Homebrew

brew install restatedev/tap/restate-server
brew install restatedev/tap/restate
brew install restatedev/tap/restatectl

Install prebuilt binaries into your npm project

npm install @restatedev/[email protected]
npm install @restatedev/[email protected]
npm install @restatedev/[email protected]

Download binary archives

View on GitHub
2025-04-15
Restate Server v1.3.1

Restate v1.3.1

Release highlights 🌟

  • Improved Admin API OpenAPI specification for better integrations with external tools.
  • Use latest RocksDB table format which provides stricter checksum validation and thereby better protection against file corruptions.
  • Improved protection against accidentally starting Restate from the wrong working directory. If restate-data contains multiple directories, then it is now required to specify the node name via --node-name or in the config via node-name, to select the right node working directory.

Fixes 🔨

  • Use the proper default configuration values when specifying the deprecated config option metadata-store. Before, it could happen that a local metadata server configured via this option would disable the WAL and thereby have weaker durability guarantees.

Install

Pull the Docker images

docker pull docker.restate.dev/restatedev/restate:1.3.1
docker pull docker.restate.dev/restatedev/restate-cli:1.3.1

Install prebuilt binaries via Homebrew

brew install restatedev/tap/restate-server
brew install restatedev/tap/restate
brew install restatedev/tap/restatectl

Install prebuilt binaries into your npm project

npm install @restatedev/[email protected]
npm install @restatedev/[email protected]
npm install @restatedev/[email protected]

Download binary archives

What’s Changed

View on GitHub
2025-04-09
Restate Server v1.3.0

Restate v1.3.0

Check out the announcement blog post for more details about Restate 1.3 and the new SDK features: https://restate.dev/blog/announcing-restate-1.3/

Deprecations 💡

  • Some config options have been replaced. The original options are still respected but will be removed in future Restate versions.
    • The config options bifrost.replicated-loglet.default-log-replication and admin.default-partition-replication have been deprecated. It is now recommended to configure default-replication instead. If you need to configure differing log and partition replication, then it is possible to do it via restatectl config set --log-replication 3 --partition-replication 2.
    • The config value admin.default-partition-replication = "everywhere" has been deprecated. When starting a new cluster with this value, then it will default to a replication of 1.
    • The config value metadata-server.type = "local" has been deprecated. In future version of Restate we are going to remove the local metadata server type. It is recommended to unset this value or configure metadata-server.type = "replicated". Restate will automatically migrate your metadata when switching from "local" to "replicated".

Install

Pull the Docker images

docker pull docker.restate.dev/restatedev/restate:1.3.0
docker pull docker.restate.dev/restatedev/restate-cli:1.3.0

Install prebuilt binaries via Homebrew

brew install restatedev/tap/restate-server
brew install restatedev/tap/restate
brew install restatedev/tap/restatectl

Install prebuilt binaries into your npm project

npm install @restatedev/[email protected]
npm install @restatedev/[email protected]
npm install @restatedev/[email protected]

Download binary archives

View on GitHub
2025-03-12
Restate Server v1.2.2

Restate v1.2.2

Release highlights 🌟

  • Improved partition processor and invoker observability (lag between applied index and log tail)
  • Restatectl improvements
    • Creating snapshots if minimum LSN is reached
    • Trim the log after creating snapshots
    • Safety checks to set log server state to read-only
  • Various UI improvements and fixes
  • Automatic log chain trimming to prevent unbounded growth

Install

Pull the Docker images

docker pull docker.restate.dev/restatedev/restate:1.2.2
docker pull docker.restate.dev/restatedev/restate-cli:1.2.2

Install prebuilt binaries via Homebrew

brew install restatedev/tap/restate-server
brew install restatedev/tap/restate
brew install restatedev/tap/restatectl

Install prebuilt binaries into your npm project

npm install @restatedev/[email protected]
npm install @restatedev/[email protected]
npm install @restatedev/[email protected]

Download binary archives

What’s Changed

New Contributors

View on GitHub
2025-02-27
Restate Server v1.2.1

Restate v1.2.1

Release highlights 🌟

Patching state from the UI 🖌️

The UI now supports patching state.

Fixes

Install

Pull the Docker images

docker pull docker.restate.dev/restatedev/restate:1.2.1
docker pull docker.restate.dev/restatedev/restate-cli:1.2.1

Install prebuilt binaries via Homebrew

brew install restatedev/tap/restate-server
brew install restatedev/tap/restate
brew install restatedev/tap/restatectl

Install prebuilt binaries into your npm project

npm install @restatedev/[email protected]
npm install @restatedev/[email protected]
npm install @restatedev/[email protected]

Download binary archives

What’s Changed

View on GitHub
2025-02-14
Restate Server v1.2.0

Restate v1.2.0: A distributed durable execution engine, built from first principles

Release Highlights 🌟

High-availability and fast fail-overs 💪

This release allows you to scale out your Restate Servers and run them in a highly-available, distributed setup. Restate runs active-active deployments, with data getting copied instantly for fast, consistent fail-over. Try deploying a multi-node cluster yourself.The single Restate server binary comes with all-batteries-included and no required external dependencies. You can start with a single node deployment and then seamlessly turn your deployment into a multi-node cluster by starting new Restate server processes. Grow the cluster yourself.

Graphical UI: Insights beyond your usual queue 🔬

This release adds a graphical UI to add an easy and intuitive way to manage, navigate, and debug your Restate applications. You can now access and query all the useful data that Restate collects about your application and answer questions like:
  • What function execution is blocking my invocation from getting executed?
  • Where in my chain of calls did my handler or workflow get stuck?
  • How many times was this function retried and which step is failing with what error?
and many more. The UI is bundled with Restate Server and accessible at the admin port http://localhost:9070.

Operational tooling 🔧

We have created a new cluster administration tool to operate a multi-node Restate deployment. With restatectl, you can check the status of your cluster, view the partitioning layout, change the configuration of your cluster, and take snapshots.

Snapshotting to object store 💾

To keep your data safe and freeing Restate from storing older data, Restate now supports creating partition store snapshots and to upload these snapshots to an object store. Check out how to configure snapshotting.

Performance improvements 🚀

This release further improves the latency and throughput of the system. Here are some latency measurements for a 3-way replicated cluster of 3 nodes under low and high load:
loadp50p75p90p99
3-step workflow549 rps (low)15ms30ms42ms69ms
9-step workflow303 rps (low)31ms45ms57ms93ms
1-step workflow23 131 rps (high)16ms20ms25ms40ms
3-step workflow16 844 rps (high)58ms67ms76ms98ms
9-step workflow8 571 rps (high)116ms126ms138ms163ms
At low load, the 3-step workflow had a median latency of 15ms. Load can be pushed to 17 000 requests per second (84 000 actions per second) with a p90 latency of 76ms.You can run this benchmark yourself.

Backward compatibility 🔙

The 1.2 release is fully backward compatible with previous Restate releases starting from version 1.1. If you have a single node deployment that you would like to turn into a multi-node deployment without losing any data, then follow the multi-node migration guide.

Managing scheduled invocations 🕐

The Restate CLI and UI show you scheduled invocations. Restate allows you to cancel and kill these invocations now.

Deprecations 💡

  • This release removes the need for a dedicated port for the metadata store. In previous releases, Restate used port 5123 for it. Now, the metadata store listens on port 5122 by default. Consequently, the config option metadata-store.bind-address has been removed.
  • The :9071 Postgres protocol port is now deprecated and will be removed in a future release. You can make queries with the cli or over http to :9070/query, which can now return JSON in addition to arrow format data.
  • Some config flags have been renamed. The old values will be accepted, but will be removed in a later version:
    • admin.log-trim-interval has been renamed to admin.log-trim-check-interval
    • allow-bootstrap has been renamed to auto-provision
    • bootstrap-num-partitions has been renamed to default-num-partitions
    • metadata-store-client has been renamed to metadata-client
    • metadata-store has been renamed to metadata-server and metadata-store.rocksdb has been flattened into metadata-server

Install

Pull the Docker images

docker pull docker.restate.dev/restatedev/restate:1.2.0
docker pull docker.restate.dev/restatedev/restate-cli:1.2.0

Install prebuilt binaries via Homebrew

brew install restatedev/tap/restate-server
brew install restatedev/tap/restate
brew install restatedev/tap/restatectl

Install prebuilt binaries into your npm project

npm install @restatedev/[email protected]
npm install @restatedev/[email protected]
npm install @restatedev/[email protected]

Download binary archives

New Contributors

View on GitHub
2024-12-25
Restate Server v1.1.6

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.View on GitHub
2024-12-11
Restate Server v1.1.5

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 scrapedView on GitHub
2024-12-09
Restate Server v1.1.4

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.
View on GitHub
2024-11-19
Restate Server v1.1.3

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)
View on GitHub
2024-09-18
Restate Server v1.1.2

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 $&#123;base_dir&#125;/$&#123;node_name&#125;/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

View on GitHub
2024-09-16
Restate Server v1.1.1

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 (https://github.com/restatedev/restate/issues/1961).

What’s Changed

View on GitHub
2024-09-09
Restate Server v1.1.0

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 (https://github.com/restatedev/restate/issues/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

View on GitHub
2024-06-21
Restate Server v1.0.2

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

View on GitHub
2024-06-11
Restate Server v1.0.1

What’s Changed

View on GitHub
2024-06-07
Restate Server v1.0.0
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

New Contributors

View on GitHub
2024-05-02
Restate Server v0.9.2
No release notes provided.View on GitHub
2024-04-30
Restate Server v0.9.1
No release notes provided.View on GitHub
2024-04-25
Restate Server v0.9.0

Restate 0.9.0 is here 🎉

The latest Restate release comes with a ton of new useful features for you. This release focuses on improving the developer experience and we highly recommend looking at our new documentation and new examples.Enjoy the release and give us feedback on discord to further improve Restate!

Notable improvements

  • Restate is now configured using the TOML format and allowing hot reloads to change Restate’s behavior w/o restarting it. Check out the configuration documentation for more details.
  • Restate now exposes many more metrics telling you what is going on under the hood.
  • Restate’s internals have been reworked to support a distributed execution very soon.

Breaking changes

The new release contains a few breaking changes that require you to start the server with a clean storage directory.

What’s Changed

New Contributors

View on GitHub
2024-03-06
Restate Server v0.8.1

What’s Changed

View on GitHub
2024-03-01
Restate Server v0.8.0

Restate 0.8.0 is here 🎉

The latest Restate release comes with a ton of new useful features for you. Enjoy the release and give us feedback on discord to further improve Restate!

Notable improvements

  • Introducing versioning information to our IDs and our stored data to support forward-compatible migrations in the future.
  • Faster discoveries by distinguishing between retryable and non-retryable errors
  • Support for grpc.reflection.v1.ServerReflection which is used by newer grpcurl versions.
  • Usage of jemalloc to prevent heap fragmentation.

Breaking changes

The new release contains a few breaking changes which require you to start the server with a clean storage directory.
  • Introducing a new format for our IDs which makes it future-proof for changes.q
View on GitHub
2024-01-31
Restate Server v0.7.1

Fixes

View on GitHub
2024-01-14
Restate Server v0.7.0

Restate 0.7.0 is here 🎉

The latest Restate release comes with a ton of new useful features for you. Enjoy the release and give us feedback on discord to further improve Restate!

New features

  • The Restate CLI is here. It provides a much simpler interaction with a running Restate server and advanced introspection and observability of what is happening.
  • We are now offering project templates with which you can get a Restate project bootstrapped with a single command via the CLI: restate examples typescript-hello-world-lambda.
  • Stopping running invocations which are no longer of interest or stuck is now possible with invocation cancelations and invocation killings. Cancelations even allow to keep your system state consistent by running compensations.
  • Deploying Restate to the cloud with one click via restate-cdk. Learn more about Restate’s CDK support.

Notable improvements

  • We are now offering new ways to install Restate’s CLI and server:
    • CLI
      • via Homebrew: brew install restatedev/tap/restate
      • via npx: npx @restatedev/restate
    • Server
      • via Homebrew: brew install restatedev/tap/restate-server
      • via npx: npx @restatedev/restate-server
    • Check out our new download page for more information.
  • We started improving Restate’s performance which lead to noticeable throughput improvements.

Breaking changes

The new release contains a few breaking changes which require you to start the server with a clean storage directory.
  • Extending the Restate protocol to make it support future use cases
  • Fixing a problem in the timer keys which lead to wrong binary orderings
  • Renaming service endpoints to service deployments which led to new REST paths
View on GitHub
2023-12-13
Restate Server v0.6.0

Breaking changes

  • Due to some breaking changes to the metadata storage format, we recommend existing users to start with a new cluster and wipe all existing state.
  • We have restricted the service key format for keyed services to only string keys. If you have any feedback about this change, let us know here https://github.com/restatedev/restate/issues/955

New features

Notable changes

  • Now the Admin API expose more metadata about service endpoints.
  • Improved DELETE /invocations/:id command
We’ve also included some bug fixes and small improvements.Enjoy!View on GitHub
2023-12-02
Restate Server v0.5.1

Fixes

  • Enable the strictest sync mode for RocksDB’s WAL.
  • Extend sys_status and sys_invocation_state with endpoint_id to make tables more expressive
View on GitHub
2023-11-18
Restate Server v0.5.0

Breaking changes

  • Due to some breaking changes to the metadata storage format, we recommend existing users to start with a new cluster and wipe all existing state.

New features

We’ve also included some bug fixes and small improvements.Enjoy!View on GitHub
2023-10-24
Restate Server v0.4.0

Breaking changes

New features

  • You can now provide an idempotency key when sending requests to Restate from an external client. This allows to implement end-to-end exactly once processing of requests. See https://docs.restate.dev/services/invocation#invoke-a-service-idempotently.
  • The introspection SQL interface has been expanded with two new tables:
    • sys_invocation_state to inspect the status of in-flight invocations.
    • sys_journal to inspect the invocation journal.
  • External ingress invocation traces now have client socket info
Among the other changes, we’ve also included a plethora of bug fixes and small improvements.Enjoy!View on GitHub
2023-09-21
Restate Server v0.3.0

Breaking changes

Due to some breaking changes to the storage format, we recommend existing users to start with a new cluster and wipe all existing state.

Changes

  • New feature: Add Kafka ingress, to read events from Kafka directly in restate services. Check the documentation https://docs.restate.dev/services/sdk/kafka for more details.
  • New feature: Now you can use the function key_to_json in SQL queries to convert the service key to json
  • Improvements: Now GET /service in the Admin API returns more metadata about service methods
  • Various fixes
View on GitHub
2023-08-26
Restate Server v0.2.1

What’s Changed

View on GitHub
2023-08-23
Restate Server v0.2.0

Breaking changes

Due to the amount of breaking changes, we recommend existing users to start with a new cluster and wipe all existing state. This release is compatible only with SDK versions starting from 0.2.0 (using the new versioning scheme).

Changes

  • Breaking: Invocation identifiers and Awakeable identifiers now have a new string format, they are shorter and bounded (both around ~30 characters). You can safely include these identifiers in path parameters, or in headers, without any risk to hit size limits. Awakeable identifiers created with a previous release are not compatible with this release.
  • New feature: Implement the dev.restate.Awakeables built-in service, to complete awakeables directly from the ingress
  • New feature: Added support to reject Awakeables, that is completing an awakeable with a failure value.
  • New feature: Added GET /endpoints in the admin api to retrieve the list of registered endpoints
  • Breaking: Modified the DELETE /invocations in the admin api to accept the id of the invocation as path parameter: DELETE /invocations/:invocation_id
  • Breaking: Modified the PartitionKey type to u64
  • Various fixes
View on GitHub
2023-08-07
Restate Server v0.1.7

Overview

  • Adding support for querying the storage via SQL. This allows getting access to the state and status table of the system which helps understanding and debugging the system.

What’s Changed

View on GitHub
2023-07-14
Restate Server v0.1.6

Overview

  • Tracing improvements. Now the traces will look more natural, as if they’re published by services. Look at the documentation to configure observability.
  • (Breaking) Upgrade and versioning of services. Registering services now works differently, and supports different service revisions. For more details, look at the documentation.

What’s Changed

View on GitHub
2023-06-27
Restate Server v0.1.5

What’s Changed

View on GitHub
2023-06-23
Restate Server v0.1.4

What’s Changed

View on GitHub
2023-06-05
Restate Server v0.1.3

What’s Changed

View on GitHub
2023-06-01
Restate Server v0.1.2

What’s Changed

View on GitHub
2023-05-18
Restate Server v0.1.1

What’s Changed

View on GitHub
2023-04-27
Restate Server v0.1.0
No release notes provided.View on GitHub