Bump Temporalio from 1.7.0 to 1.9.0 #227
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
--- updated-dependencies: - dependency-name: Temporalio dependency-version: 1.9.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 Temporalio from 1.7.0 to 1.9.0.
Release notes
Sourced from Temporalio's releases.
1.9.0
Get from NuGet and read the README
Highlights
Environment Configuration Support (experimental)
Users can now use
Temporalio.Client.EnvConfig.ClientEnvConfigto load environment configuration from config files or environment variables. This is the same configuration approach that can be used across other SDKs and CLI. See https://docs.temporal.io/develop/environment-configuration for more details.Nexus Support (experimental)
The Nexus .NET SDK has been released and this release adds Temporal support for implementing Nexus services with Temporal and calling Nexus services from Temporal workflows. See the Temporal SDK Developer Guide, Nexus SDK README, the Temporal SDK README section, and the initial Nexus .NET sample.
💥 MINOR BREAKING BEHAVIOR CHANGE - Serialization Context Change in Workflows
For advanced users of custom converters/codecs that were also leveraging the recent serialization context feature, there is a slight change in how they are handled in workflows. Previously, we eagerly created and used the converter/codec for all workflow use with the singular workflow context which meant we "stacked" contexts when they were also used for activities and children and such. Now we are properly not stacking the outer workflow context when making these other calls. So technically if there was a custom converter using advanced serialization contexts that relied on this context stacking, this can be a breaking change. See the PR at temporalio/sdk-dotnet#525 for more details.
Specific Changes
2025-09-18 - 45e61c8 - Activity reset (#521)
2025-09-18 - 95f840a - Fixed error message of
BinaryProtoConverter.AssertProtoPayloadnot filling a placeholder (#520)2025-09-22 - 2319df1 - Added retry policy to activity info (#511)
2025-09-22 - 8db923c - Env config (#509)
2025-09-22 - da7202a - Nexus support (#517)
2025-09-22 - e29940d - Added summary to local activity options (#524)
2025-09-25 - d4a0765 - Update version to 1.9.0 (#527)
2025-09-25 - f99bca3 - 💥 Fix how serialization context is applied in workflows [MINOR COMPAT BREAK] (#525)
2025-09-25 - fad7fb3 - Fix issue with search attribute keyword list type (#529)
1.8.0
Get from NuGet and read the README
Highlights
💥 BREAKING CHANGE - C bridge has been moved to Core SDK repository, library file names have changed
The C bridge library used to integrate .Net SDK with Core SDK has been moved to facilitate using it for SDKs in other languages. As part of the move, the bridge library, its functions and its artifacts have been given more specific names.
Previously, the C bridge library had the filename
temporal_sdk_bridge.dllon Windows,libtemporal_sdk_bridge.soon Linux, andlibtemporal_sdk_bridge.dylibon macOS.The filename has changed to
temporal_sdk_core_c_bridge.dllon Windows,libtemporal_sdk_core_c_bridge.soon Linux, andlibtemporal_sdk_core_c_bridge.dylibon macOS.If your build process depends on the exact naming of these files, it needs to be updated to use the new file names. Furthermore, if you were using the C bridge library directly, there have been further breaking changes in the library itself. See the following Core SDK PR for details: temporalio/sdk-core#951
Task Queue Fairness Support (experimental)
This release adds support for Task Queue Fairness. Fairness is a new feature of Temporal's task queues that allows for more control over the order that tasks are dispatched from a backlog. It's intended to address common situations like multi-tenant applications and reserved capacity bands.
This is in addition to "Workflow & Activity Priorities" provided last release.
Specific Changes
2025-06-18 - 165569d - Deprecate VersioningIntent (#491)
2025-06-26 - 99847b5 - Add defaults for Poller automation (#493)
2025-06-30 - d1fedb0 - Fix issue where child workflow starts and completes in same activation (#492)
2025-07-02 - 8e94382 - Moved C Bridge from dotnet-sdk to core-sdk repo (💥 BREAKING CHANGE) (#494)
2025-07-16 - 2a7621c - Remove experimental notices from update with start calls (#497)
2025-07-17 - 5b15fb8 - Missed an UwS experimental warning (#498)
2025-08-04 - f225d76 - Remove CLI version pin for internal tests (#501)
2025-08-07 - b55175e - Made
TemporalWorker.ExecuteAsync()keep working even afterDispose()(#503)2025-08-11 - 6f27e45 - Do not require heartbeating to be done in context (#504)
2025-08-22 - deb2756 - Fairness Keys & Weights (#508)
2025-09-02 - 77f839d - Added FirstExecutionRunId to WorkflowInfo (#516)
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)