updates from 8/12

Signed-off-by: Hannah Hunter <[email protected]>

daprblog/content/posts/2024/v1.14-release.md

@@ -27,7 +27,7 @@ Many applications require job scheduling, or the need to take an action in the f
 
 Dapr’s Jobs API ensures the tasks represented in these types of scenarios are performed consistently and reliably, improving efficiency and reducing the risk of errors. Think of this as a scalable version of the popular Dapr [Cron Binding](https://docs.dapr.io/reference/components-reference/supported-bindings/cron/), now as a first class API available throught the Dapr SDKs.
 
-You can read more in the [Jobs API overview](https://v1-14.docs.dapr.io/developing-applications/building-blocks/jobs/jobs-overview/) documentation, or dive into a [Quickstart Go code example](https://v1-14.docs.dapr.io/getting-started/quickstarts/jobs-quickstart/). 
+You can read more in the [Jobs API overview](https://v1-14.docs.dapr.io/developing-applications/building-blocks/jobs/jobs-overview/) documentation, or dive into a [Quickstart Go code example](https://v1-14.docs.dapr.io/getting-started/quickstarts/jobs-quickstart/). Support for Jobs is also in the Alpha Rust-SDK!
 
 #### Scheduler service (preview)
 The [Scheduler service](https://v1-14.docs.dapr.io/concepts/dapr-services/scheduler/) is a new [control plane service](https://v1-14.docs.dapr.io/concepts/overview/#kubernetes) used to schedule jobs, running in self-hosted mode or on Kubernetes. It is installed by when using the Dapr CLI and is the service responsible for managing the scheduled jobs.
@@ -52,7 +52,7 @@ spec:
 ### Streaming subscriptions (preview)
 [Streaming subscription are a new type of subscription written in code](https://v1-14.docs.dapr.io/developing-applications/building-blocks/pubsub/subscription-methods/). Streaming subscriptions are dynamic, meaning they allow for adding or removing subscriptions at runtime. They do not require a subscription HTTP endpoint in your application (that is required by the current programmatic and declarative subscriptions), making them easy to configure in code. Streaming subscriptions also do not require an app to be configured with the sidecar to receive messages. These are an [incredibly easy way to configure topic subscriptions](https://v1-14.docs.dapr.io/developing-applications/building-blocks/pubsub/subscription-methods/#streaming-subscriptions) for your app.
 
-### Actor multi-tenancy with namespacing 
+### Actor multi-tenancy with namespacing
 Namespacing in Dapr provides [isolation](https://v1-14.docs.dapr.io/concepts/isolation-concept/), and thus multi-tenancy. With [actor namespacing](https://v1-14.docs.dapr.io/developing-applications/building-blocks/actors/namespaced-actors/), the same actor type can be deployed into different namespaces. You can then call instances of these actors within the same namespace. Each namespaced actor deployment must use its own separate state store, especially if the same actor type is used across namespaces.
 
 
@@ -73,11 +73,11 @@ When using the [outbox pattern](https://v1-14.docs.dapr.io/developing-applicatio
 The ability to invoke non-Dapr endpoints using the Dapr [Service invocation API](https://docs.dapr.io/developing-applications/building-blocks/service-invocation/howto-invoke-non-dapr-endpoints/)is now stable.
 
 ### Dapr Shared ([new preview repo in Dapr org](https://github.com/dapr/dapr-shared/blob/main/README.md))
-Although not part of the Dapr runtime v1.14 release, [Dapr Shared provides alternative deployment choices for Dapr](https://docs.dapr.io/operations/hosting/kubernetes/kubernetes-dapr-shared/). 
+Although not part of the Dapr runtime v1.14 release, [Dapr Shared provides alternative deployment choices for Dapr](https://docs.dapr.io/operations/hosting/kubernetes/kubernetes-dapr-shared/).
 
-Dapr, by default, is injected as a sidecar to enable the Dapr APIs for your applications for the best availability and reliability. Dapr Shared enables two alternative deployment strategies to create Dapr applications using a **Kubernetes Daemonset for a per-node deployment** or a **Deployment for a per-cluster** deployment. 
+Dapr, by default, is injected as a sidecar to enable the Dapr APIs for your applications for the best availability and reliability. Dapr Shared enables two alternative deployment strategies to create Dapr applications using a **Kubernetes Daemonset for a per-node deployment** or a **Deployment for a per-cluster** deployment.
 
-For example, Dapr Shared can be used to reduce resource usage in a cluster or to make a simpler testing deployment environment. 
+For example, Dapr Shared can be used to reduce resource usage in a cluster or to make a simpler testing deployment environment.
 
 ### Support for cryptography api in the python sdk
 The python-sdk now has support for the cryptography api.
@@ -250,6 +250,7 @@ Thanks to everyone who made this release possible!
 - **FIXED** Repository bot no longer returns an error for non-assign comments and also … [149](https://github.com/dapr/rust-sdk/pull/149)
 - **DOCUMENTED** Initialise docs  [181](https://github.com/dapr/rust-sdk/pull/181)
 - **UPDATED** chore: bump to rc.4 [195](https://github.com/dapr/rust-sdk/pull/195)
+- **ADDED** feat: Jobs/Scheduler API [196](https://github.com/dapr/rust-sdk/pull/196)
 ### JavaScript SDK
 - **FIXED** "TypeError: Converting circular structure to JSON" while using custom winston logger service [488](https://github.com/dapr/js-sdk/issues/488)
 - **FIXED** Update the holopin.yaml to use the sdk badge [589](https://github.com/dapr/js-sdk/issues/589)
@@ -328,7 +329,6 @@ To upgrade Dapr using Helm, run:
 ```
 helm repo add dapr https://dapr.github.io/helm-charts/
 helm repo update
-
 helm upgrade dapr dapr/dapr --version 1.14 --namespace=dapr-system --wait
 ```
 
@@ -346,9 +346,7 @@ You can use Helm 3 to install Dapr:
 ```
 helm repo add dapr https://dapr.github.io/helm-charts/
 helm repo update
-
 kubectl create namespace dapr-system
-
 helm install dapr dapr/dapr --version 1.14 --namespace dapr-system --wait
 ```
 
@@ -385,6 +383,9 @@ kubectl rollout restart deploy/<deployment-name>
 - **ADDED** State serializer content type when saving actor states. [1033](https://github.com/dapr/java-sdk/pull/1033)
   - This change can make data to be saved in a different format in the state store, causing previous data not to be read. It is recommended for users to test the new SDK using non-production state store where data was saved with the previous SDK version to confirm it will not cause issues.
 
+### Actor placement (cross-namespace actor invocation)
+Actors are now namespaced, meaning that cross-namespace actor invocation is no longer supported. You must ensure that all actor invocations occur within the same namespace.
+
 ## Deprecation Notices
 
 None.