Releases: dapr/dotnet-sdk
Releases · dapr/dotnet-sdk
Dapr dotnet-sdk v1.9.0-rc01 (Pre-release)
What's Changed
- Add client docs for Configuration Subscribe API by @halspang in #895
- Fix the problem of determining whether there is a MetadataSeparator error by @saber-wang in #900
- Add Actor Reminder/Timer TTL support by @halspang in #912
- Update Dapr and CLI to 1.8 by @halspang in #893
- FIX Allow actor healthz endpoint are now always AllowAnonymous by @mcandeia in #923
- Upgrade grpc.tools version to 2.47.0 for supporting arm64 architecture by @mcandeia in #920
- Update SDK to reflect renaming on UnlockResponse.Status by @tmacam in #924
- Update dotnet-daprclient-usage.md by @dss539 in #930
- Add dead letter topic support by @yash-nisar in #929
- Add support for shutdown API and add client docs by @halspang in #922
- Added new links to client folder in example by @amulyavarote in #938
- topicmetadata should allow adding empty strings by @saber-wang in #940
- Added exception details to the actor invocation by @amulyavarote in #931
- Change log level to information in pubsub examples by @yash-nisar in #942
- [Docs refresh] Actors section refresh by @hhunter-ms in #918
- Configuration API changes to support dictionary type response by @amulyavarote in #943
- Added actor method exception details docs by @amulyavarote in #950
- Add dapr-bot support to assign issues by @yash-nisar in #951
- add metadata api by @saber-wang in #947
New Contributors
- @mcandeia made their first contribution in #923
- @tmacam made their first contribution in #924
- @dss539 made their first contribution in #930
- @yash-nisar made their first contribution in #929
Full Changelog: v1.8.0...v1.9.0-rc01
Contributors
tmacam, mcandeia, and 6 other contributors
Assets 2
Dapr dotnet-sdk v1.8.0
v1.8 Changes
- ADDED When publishing a message allow setting Cloudevent attributes / Pub-Sub routing 773
- ADDED Support for Configuration Subscribe API 822
- FIXED App API Token support 835
- ADDED FOSSA Scan to Build Actions 843
- ADDED Support for Per Actor Type Configuration 857
- ADDED Enable raw metadata for Pub/Sub with .WithTopic<> Extension. 860
- FIXED Move AddDaprClient in Dapr.AspNetCore from AddSingleton to TryAddSingleton 867
- ADDED Subscription supports adding custom metadata 873
- ADDED Support for Distributed Lock API 885
Dapr dotnet-sdk v1.8.0-rc01 (Pre-release)
Added dotnet methods for Distributed Lock API (#886) * Added dotnet methods for Distributed Lock API Signed-off-by: Amulya Varote <[email protected]> * Changes based on the review comments Signed-off-by: Amulya Varote <[email protected]> * Changes in examples to make them real world - based on the PR review Signed-off-by: Amulya Varote <[email protected]> * Fixed application log statements Signed-off-by: Amulya Varote <[email protected]> * Changes to implement IDisposable Signed-off-by: Amulya Varote <[email protected]> * Changes based on the review comments Signed-off-by: Amulya Varote <[email protected]> * Added a sample test case for TryLockResponse Signed-off-by: Amulya Varote <[email protected]> * Changes based on the review comments - 2 Signed-off-by: Amulya Varote <[email protected]> * Reworking the DistributedLock example Signed-off-by: Hal Spang <[email protected]> Co-authored-by: Hal Spang <[email protected]>
Dapr dotnet-sdk v1.7.0
Dapr dotnet-sdk v1.7.0-rc01 (Pre-release)
Update Google.Protobuf to 3.15 (#850) Signed-off-by: Hal Spang <[email protected]>
Dapr dotnet-sdk v1.6.0
Fix issue where state did not reset on actor error (#789) When an actor call fails, it is imperative that the state is reset. In the remoting path, we were catching the exception and returning an error response instead of propagating the exception. Without this, the error path was never triggered. This allowed for state from failed requests to persist on subsequent requests. https://github.com/dapr/dotnet-sdk/issues/762 Signed-off-by: Hal Spang <[email protected]>
Dapr dotnet-sdk v1.6.0-rc01 (Pre-release)
Fix issue where state did not reset on actor error (#789) When an actor call fails, it is imperative that the state is reset. In the remoting path, we were catching the exception and returning an error response instead of propagating the exception. Without this, the error path was never triggered. This allowed for state from failed requests to persist on subsequent requests. https://github.com/dapr/dotnet-sdk/issues/762 Signed-off-by: Hal Spang <[email protected]>
Dapr dotnet-sdk v1.5.0
Allow multiple topics to call the same endpoint (#763) * Allow multiple topics to call the same endpoint Using the WithTopic builder pattern allows you to specify multiple topics that route to a single endpoint. Given the topics are unique, this should be a valid case. This change allows for a single endpoint to bind to multiple topics. Note that this can only be done via the EndpointBuilder and not the TopicAttribute. https://github.com/dapr/dotnet-sdk/issues/715 * Let TopicAttribute to be specified multiple times The endpoint builder allowed for multiple WithTopic calls so the attribute should match that behavior.
Dapr dotnet-sdk v1.4.0
Add an option to set Timeout for ActorProxy (#748) * Add an option to set Timeout for ActorProxy Actors, by there nature, may have to wait for a long period before being allowed to execute. This could lead to long request times. The default timeout for the HttpClient being used is fairly low. This commit allows for the timeout to be set when constructing the proxy. https://github.com/dapr/dotnet-sdk/issues/728 * Removed extra constructor and e2e tests.
Dapr dotnet-sdk v1.4.0-rc (prerelease)
Add an option to set Timeout for ActorProxy (#748) * Add an option to set Timeout for ActorProxy Actors, by there nature, may have to wait for a long period before being allowed to execute. This could lead to long request times. The default timeout for the HttpClient being used is fairly low. This commit allows for the timeout to be set when constructing the proxy. https://github.com/dapr/dotnet-sdk/issues/728 * Removed extra constructor and e2e tests.