Bump Dapr.AspNetCore from 1.13.0 to 1.16.0 #33
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated Dapr.AspNetCore from 1.13.0 to 1.16.0.
Release notes
Sourced from Dapr.AspNetCore's releases.
1.16.0
The v1.16 release of the Dapr .NET SDK delivers a set of targeted enhancements focused on developer productivity and runtime efficiency. Most notably, this version debuts Roslyn analyzers and accompanying code fixes that enforce best practices around SDK configuration and usage. This marks the beginning of a more guided and prescriptive development experience, reducing setup complexity and surfacing misconfigurations early.
Framework support has been consolidated with the depreciation of .NET 6 and 7, aligning the SDK with .NET 8 and 9. This shift enabled internal refactoring that improves performance and resource utilization across core components.
On the feature front, the SDK now supports the latest capabilities in the Dapr conversation API with tooling, as well as the overwrite flag for job scheduling. A critical bug affecting encryption and decryption of large files exceeding 4 GB has been resolved.
Dapr Workflows orchestrated using the .NET SDK are now considered stable, supporting both short-lived and long-running processes. Performance has been further improved through targeted optimizations, including new helper methods that enable deterministic parallelization with bounded concurrency.
Maintainer's Note
I wanted to share a special shout-out to everyone that participated in this release. Without your work to find and report issues in Discord or GitHub, spot documentation inconsistencies, request features, submit pull requests, review others' pull requests or even just use the various parts of the Dapr .NET SDK in your projects - I heartily appreciate the effort you've put into this project. The project wouldn't be what it is without your help. Thank you!
What's Changed
Please refer to the release notes here for the most accurate representation of what's changed.
New Contributors
Full Changelog: dapr/dotnet-sdk@v1.15.0...v1.16.0
1.16.0-rc18
What's Changed
Full Changelog: dapr/dotnet-sdk@v1.16.0-rc17...v1.16.0-rc18
1.16.0-rc17
What's Changed
Full Changelog: dapr/dotnet-sdk@v1.16.0-rc16...v1.16.0-rc17
1.16.0-rc16
What's Changed
Full Changelog: dapr/dotnet-sdk@v1.16.0-rc15...v1.16.0-rc16
1.16.0-rc13
What's Changed
DaprJobScheduletype and examples by @WhitWaldo in Updated docs to reflectDaprJobScheduletype and examples dapr/dotnet-sdk#1605Also (need to look up the PRs for in the release notes):
DateTimeOffsetin addition toDateTimeFinally, this release added analyzers and code fixes across Workflow, Actors and Jobs functionality to help eliminate some common errors seen in Discord. You can read more about this in the not-yet-published documentation here
New Contributors
Full Changelog: dapr/dotnet-sdk@v1.15.4...v1.16.0-rc13
1.16.0-rc03
What's Changed
Full Changelog: dapr/dotnet-sdk@v1.16.0-rc02...v1.16.0-rc03
1.16.0-rc02
This is a follow-up to the v1.16.0-rc01 prerelease build deployed last week and fixes another related set of issues that came to light after the outer timeout issue was discovered.
Like the rest of the 1.16 releases will be, this only supports the .NET 8 and .NET 9 targets and does not support .NET 6 or .NET 7. That said, like the previous 1.16.0-rc01 prerelease, this also excludes all the 1.16 feature releases and is fully compatible with the latest 1.15 Dapr runtime.
Please don't hesitate to reach out for assistance here or via our Dapr Discord channel if you have any questions about this.
What's Changed
Full Changelog: dapr/dotnet-sdk@v1.16.0-rc01...v1.16.0-rc02
1.16.0-rc01
This is an out-of-band patch release to address an issue raised with workflows timing out and reconnecting frequently when they're either idle or activities run for a long period of time.
It is released as a release candidate on the 1.16 series because it only supports .NET 8 and .NET 9 targets (which 1.16 will be limited to as well) and does not also include support for the .NET 6 and .NET 7 targets that 1.15 targets.
That said, none of the functionality currently being built out for the 1.16 release is included in this RC, but it does include all the patches up to the most recent 1.15 release, so if you're targeting .NET 8 or .NET 9, you should be able to safely consume this package without fear of significant changes more common to the main Dapr releases.
1.15.4
What's Changed
This release fixes a reported issue regarding issues connecting (and reconnecting) to the scheduler when using .NET 9 and
Dapr.Workflows.Full Changelog: dapr/dotnet-sdk@v1.15.3...v1.15.4
1.15.3
What's Changed
Full Changelog: dapr/dotnet-sdk@v1.15.2...v1.15.3
1.15.2
What's Changed
This allows for actor reminders to be properly deserialized even if the
PeriodorTTLfields includes a duration expression (e.g.@weeklyor@every 1.5h25s). Do note that because of how the current Actors API is shaped, it requires deserialization to aTimeSpanas opposed to how we approach this inDapr.Jobsand deserialize all available formats to aDaprJobSchedule. As a result, some of theTimeSpanreturn values may not make a lot of sense; for example one can't really express@midnightas a timespan despite being an allowed duration expression. Rather, this will deserialize asnew TimeSpan()with all zeroed-out values.As later Dapr releases increasing target improvements to Actors, we'll look into opportunities to revisit this approach and make it more consistent with other Dapr APIs like the aforementioned
Dapr.Jobs.Full Changelog: dapr/dotnet-sdk@v1.15.1...v1.15.2
1.15.1
What's Changed
ConversationOptionsnot accepting unsetConversationIdby @WhitWaldo in FixedConversationOptionsnot accepting unsetConversationIddapr/dotnet-sdk#1480Full Changelog: dapr/dotnet-sdk@v1.15.0...v1.15.1
1.15.0
I'd like to thank everyone who contributed to the 1.15.0 release - your help is invaluable and I appreciate it!
What's Changed
DaprConfigurationStoreProvidernot applying case-insensitive configuration updates correctly. 934GetJobAsyncdeserialization issue 1461... (truncated)
1.15.0-rc07
What's Changed
Full Changelog: dapr/dotnet-sdk@v1.15.0-rc06...v1.15.0-rc07
1.15.0-rc06
What's Changed
Full Changelog: dapr/dotnet-sdk@v1.15.0-rc05...v1.15.0-rc06
1.15.0-rc05
What's Changed
GetJobAsyncdeserialization issue by @WhitWaldo in Fix forGetJobAsyncdeserialization issue dapr/dotnet-sdk#1461Full Changelog: dapr/dotnet-sdk@v1.15.0-rc04...v1.15.0-rc05
1.15.0-rc04
What's Changed
Full Changelog: dapr/dotnet-sdk@v1.15.0-rc03...v1.15.0-rc04
1.15.0-rc03
What's Changed
Full Changelog: dapr/dotnet-sdk@v1.15.0-rc02...v1.15.0-rc03
1.15.0-rc02
What's Changed
Full Changelog: dapr/dotnet-sdk@v1.15.0-rc01...v1.15.0-rc02
1.15.0-rc01
What's Changed
master. by @philliphoff in Merge 1.14 release branch back intomaster. dapr/dotnet-sdk#1337... (truncated)
1.14.0
What's Changed
Valueproperty as nullable by @WhitWaldo in Marked bulk stateValueproperty as nullable dapr/dotnet-sdk#1259release-1.13back intomasterby @philliphoff in Mergerelease-1.13back intomasterdapr/dotnet-sdk#1285New Contributors
Full Changelog: dapr/dotnet-sdk@v1.13.1...v1.14.0
1.14.0-rc02
What's Changed
New Contributors
Full Changelog: dapr/dotnet-sdk@v1.14.0-rc01...v1.14.0-rc02
1.14.0-rc01
Breaking Changes
With 1.14, explicit support for .NET 7 (such as it is) in the SDK is considered deprecated. Starting with 1.15, no Dapr SDK assemblies will target .NET 7 (but .NET 7 applications may still be able to use the .NET 6 targeted assemblies).
What's Changed
Valueproperty as nullable by @WhitWaldo in Marked bulk stateValueproperty as nullable dapr/dotnet-sdk#1259release-1.13back intomasterby @philliphoff in Mergerelease-1.13back intomasterdapr/dotnet-sdk#1285New Contributors
Full Changelog: dapr/dotnet-sdk@v1.13.1...v1.14.0-rc01
1.13.1
What's Changed
Full Changelog: dapr/dotnet-sdk@v1.13.0...v1.13.1
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)