Added release note for SDK typescript and latest runtime release.

restatedev · Sep 25, 2024 · 21ca902 · 21ca902
1 parent e7d271c
commit 21ca902
Show file tree

Hide file tree

Showing 3 changed files with 9 additions and 3 deletions.
diff --git a/README.md b/README.md
@@ -56,7 +56,9 @@ The compatibility with Restate is described in the following table:
 | Restate Server\sdk-typescript | 1.0/1.1/1.2/1.3 | 
 |-------------------------------|-----------------|
 | 1.0                           | ✅               |
-| 1.1                           | ✅               |
+| 1.1 <sup>(1)</sup>            | ✅               |
+
+<sup>(1)</sup> When upgrading from 1.0 to 1.1, due to a bug in the service discovery, you need to run re-discovery **all the existing deployments** using `restate dp register <address> --force`. You don't need to update the SDK, nor change the code. New deployments will work fine regardless of the SDK version, without any further workarounds. 
 
 ## Contributing
 

diff --git a/packages/restate-sdk-core/README.md b/packages/restate-sdk-core/README.md
@@ -56,4 +56,6 @@ The compatibility with Restate is described in the following table:
 | Restate Server\sdk-typescript | 1.0/1.1/1.2/1.3 | 
 |-------------------------------|-----------------|
 | 1.0                           | ✅               |
-| 1.1                           | ✅               |
+| 1.1 <sup>(1)</sup>            | ✅               |
+
+<sup>(1)</sup> When upgrading from 1.0 to 1.1, due to a bug in the service discovery, you need to run re-discovery **all the existing deployments** using `restate dp register <address> --force`. You don't need to update the SDK, nor change the code. New deployments will work fine regardless of the SDK version, without any further workarounds. 
diff --git a/packages/restate-sdk/README.md b/packages/restate-sdk/README.md
@@ -56,4 +56,6 @@ The compatibility with Restate is described in the following table:
 | Restate Server\sdk-typescript | 1.0/1.1/1.2/1.3 | 
 |-------------------------------|-----------------|
 | 1.0                           | ✅               |
-| 1.1                           | ✅               |
+| 1.1 <sup>(1)</sup>            | ✅               |
+
+<sup>(1)</sup> When upgrading from 1.0 to 1.1, due to a bug in the service discovery, you need to run re-discovery **all the existing deployments** using `restate dp register <address> --force`. You don't need to update the SDK, nor change the code. New deployments will work fine regardless of the SDK version, without any further workarounds.