Skip to content

Bump the temporal group with 4 updates #152

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Bump the temporal group with 4 updates #152

wants to merge 1 commit into from
+4 −4

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 1, 2025 •
edited
Loading

Updated Temporalio from 1.6.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.ClientEnvConfig to 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.

⚠️ This is experimental and subject to change.

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 Nexus SDK README, the Temporal SDK README section, and the initial Nexus .NET sample.

⚠️ This is experimental and subject to change.

💥 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.AssertProtoPayload not 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.dll on Windows, libtemporal_sdk_bridge.so on Linux, and libtemporal_sdk_bridge.dylib on macOS.

The filename has changed to temporal_sdk_core_c_bridge.dll on Windows, libtemporal_sdk_core_c_bridge.so on Linux, and libtemporal_sdk_core_c_bridge.dylib on 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 after Dispose() (#​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)

1.7.0

Get from NuGet and read the README

Highlights

Workflow & Activity Priorities

Users can now set a priority key when scheduling a workflow, activity or child workflows. The priority key will be used to help prioritize certain tasks over others when there is a backlog. Priority is currently not supported in any OSS Temporal release, but support will be coming soon. To experiment with this feature please see the pre-release development server or if you are a Temporal Cloud customer reach out to your SA.

Worker deployment versioning preview

This release introduces a preview of new APIs that gracefully manage code changes and worker pools that support them. The goal is to better control which workers should execute new, and existing, workflows and activities tasks, based on their code and configuration.

VersioningBehavior.AutoUpgrade and VersioningBehavior.Pinned are two Versioning Behaviors that can be specified on a workflow implementation using the VersioningBehavior argument to the Workflow attribute. Pinned workflows are typically short lived, and are never affected by new versions, i.e., they do not need to use the patch API for compatibility. AutoUpgrade workflows are mostly long running, but they need to use patching to safely transition to new versions. The choice of Pinned vs AutoUpgrade ultimately depends on your willingness to keep old worker fleets running vs the complexity of patching.

To manage Worker Deployments please use the Temporal CLI, or Temporalio.Client.WorkflowService

Automatic Poller Scaling

You can configure Workers to automatically adjust the number of concurrent polls they make for tasks! Set the WorkflowTaskPollerBehavior and ActivityTaskPollerBehavior arguments of the Worker options to PollerBehavior.Autoscaling to try it out. You can expect fewer unnecessary polls during low load, and increased polls during high load when they can be used to increase task throughput.

Activity pause support

Activity pausing (not GA currently) will now cancel the activity cancellation token thereby interrupting activity execution similar to how activity cancel and worker shut down does. There is a new CancellationDetails property on the ActivityExecutionContext that provides the reason for cancellation token being set.

Specific Changes

2025-04-28 - 98db10f - Add CODEOWNERS (#​467)
2025-04-28 - d48377d - Handle errors with update result serialization (#​468)
2025-04-28 - dcf7e1c - Replace BuildJet in build-binary smoke test (#​469)
2025-05-08 - 1890573 - Fail the workflow task if a requested local activity is not registered (#​472)
2025-05-14 - 4205a59 - Expose poller automation (#​477)
2025-05-14 - cbf20f9 - Worker Deployment Versioning (#​466)
2025-05-16 - 910fb1c - Improve/verbosify error messages in various ToInteropOptions methods (#​481)
2025-05-19 - 8918a31 - Properly restore auto-time-skipping after disabled (#​475)
2025-05-19 - b94084b - Add WorkflowInfo.WorkflowStartTime (#​476)
2025-05-27 - 864e654 - Activity pause support (#​482)
2025-05-29 - fa93167 - Added Category to ApplicationFailureException (#​483)
2025-06-06 - 761465d - Updated sdk-core to latest (#​485)
2025-06-06 - a7ca5ec - Make static summary/details lazy on workflow description (#​486)

Commits viewable in compare view.

Updated Temporalio.Extensions.DiagnosticSource from 1.6.0 to 1.9.0.

Release notes

Sourced from Temporalio.Extensions.DiagnosticSource's releases.

1.9.0

Get from NuGet and read the README

Highlights

Environment Configuration Support (experimental)

Users can now use Temporalio.Client.EnvConfig.ClientEnvConfig to 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.

⚠️ This is experimental and subject to change.

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 Nexus SDK README, the Temporal SDK README section, and the initial Nexus .NET sample.

⚠️ This is experimental and subject to change.

💥 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.AssertProtoPayload not 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.dll on Windows, libtemporal_sdk_bridge.so on Linux, and libtemporal_sdk_bridge.dylib on macOS.

The filename has changed to temporal_sdk_core_c_bridge.dll on Windows, libtemporal_sdk_core_c_bridge.so on Linux, and libtemporal_sdk_core_c_bridge.dylib on 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 after Dispose() (#​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)

1.7.0

Get from NuGet and read the README

Highlights

Workflow & Activity Priorities

Users can now set a priority key when scheduling a workflow, activity or child workflows. The priority key will be used to help prioritize certain tasks over others when there is a backlog. Priority is currently not supported in any OSS Temporal release, but support will be coming soon. To experiment with this feature please see the pre-release development server or if you are a Temporal Cloud customer reach out to your SA.

Worker deployment versioning preview

This release introduces a preview of new APIs that gracefully manage code changes and worker pools that support them. The goal is to better control which workers should execute new, and existing, workflows and activities tasks, based on their code and configuration.

VersioningBehavior.AutoUpgrade and VersioningBehavior.Pinned are two Versioning Behaviors that can be specified on a workflow implementation using the VersioningBehavior argument to the Workflow attribute. Pinned workflows are typically short lived, and are never affected by new versions, i.e., they do not need to use the patch API for compatibility. AutoUpgrade workflows are mostly long running, but they need to use patching to safely transition to new versions. The choice of Pinned vs AutoUpgrade ultimately depends on your willingness to keep old worker fleets running vs the complexity of patching.

To manage Worker Deployments please use the Temporal CLI, or Temporalio.Client.WorkflowService

Automatic Poller Scaling

You can configure Workers to automatically adjust the number of concurrent polls they make for tasks! Set the WorkflowTaskPollerBehavior and ActivityTaskPollerBehavior arguments of the Worker options to PollerBehavior.Autoscaling to try it out. You can expect fewer unnecessary polls during low load, and increased polls during high load when they can be used to increase task throughput.

Activity pause support

Activity pausing (not GA currently) will now cancel the activity cancellation token thereby interrupting activity execution similar to how activity cancel and worker shut down does. There is a new CancellationDetails property on the ActivityExecutionContext that provides the reason for cancellation token being set.

Specific Changes

2025-04-28 - 98db10f - Add CODEOWNERS (#​467)
2025-04-28 - d48377d - Handle errors with update result serialization (#​468)
2025-04-28 - dcf7e1c - Replace BuildJet in build-binary smoke test (#​469)
2025-05-08 - 1890573 - Fail the workflow task if a requested local activity is not registered (#​472)
2025-05-14 - 4205a59 - Expose poller automation (#​477)
2025-05-14 - cbf20f9 - Worker Deployment Versioning (#​466)
2025-05-16 - 910fb1c - Improve/verbosify error messages in various ToInteropOptions methods (#​481)
2025-05-19 - 8918a31 - Properly restore auto-time-skipping after disabled (#​475)
2025-05-19 - b94084b - Add WorkflowInfo.WorkflowStartTime (#​476)
2025-05-27 - 864e654 - Activity pause support (#​482)
2025-05-29 - fa93167 - Added Category to ApplicationFailureException (#​483)
2025-06-06 - 761465d - Updated sdk-core to latest (#​485)
2025-06-06 - a7ca5ec - Make static summary/details lazy on workflow description (#​486)

Commits viewable in compare view.

Updated Temporalio.Extensions.Hosting from 1.6.0 to 1.9.0.

Release notes

Sourced from Temporalio.Extensions.Hosting's releases.

1.9.0

Get from NuGet and read the README

Highlights

Environment Configuration Support (experimental)

Users can now use Temporalio.Client.EnvConfig.ClientEnvConfig to 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.

⚠️ This is experimental and subject to change.

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 Nexus SDK README, the Temporal SDK README section, and the initial Nexus .NET sample.

⚠️ This is experimental and subject to change.

💥 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.AssertProtoPayload not 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.dll on Windows, libtemporal_sdk_bridge.so on Linux, and libtemporal_sdk_bridge.dylib on macOS.

The filename has changed to temporal_sdk_core_c_bridge.dll on Windows, libtemporal_sdk_core_c_bridge.so on Linux, and libtemporal_sdk_core_c_bridge.dylib on 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 after Dispose() (#​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)

1.7.0

Get from NuGet and read the README

Highlights

Workflow & Activity Priorities

Users can now set a priority key when scheduling a workflow, activity or child workflows. The priority key will be used to help prioritize certain tasks over others when there is a backlog. Priority is currently not supported in any OSS Temporal release, but support will be coming soon. To experiment with this feature please see the pre-release development server or if you are a Temporal Cloud customer reach out to your SA.

Worker deployment versioning preview

This release introduces a preview of new APIs that gracefully manage code changes and worker pools that support them. The goal is to better control which workers should execute new, and existing, workflows and activities tasks, based on their code and configuration.

VersioningBehavior.AutoUpgrade and VersioningBehavior.Pinned are two Versioning Behaviors that can be specified on a workflow implementation using the VersioningBehavior argument to the Workflow attribute. Pinned workflows are typically short lived, and are never affected by new versions, i.e., they do not need to use the patch API for compatibility. AutoUpgrade workflows are mostly long running, but they need to use patching to safely transition to new versions. The choice of Pinned vs AutoUpgrade ultimately depends on your willingness to keep old worker fleets running vs the complexity of patching.

To manage Worker Deployments please use the Temporal CLI, or Temporalio.Client.WorkflowService

Automatic Poller Scaling

You can configure Workers to automatically adjust the number of concurrent polls they make for tasks! Set the WorkflowTaskPollerBehavior and ActivityTaskPollerBehavior arguments of the Worker options to PollerBehavior.Autoscaling to try it out. You can expect fewer unnecessary polls during low load, and increased polls during high load when they can be used to increase task throughput.

Activity pause support

Activity pausing (not GA currently) will now cancel the activity cancellation token thereby interrupting activity execution similar to how activity cancel and worker shut down does. There is a new CancellationDetails property on the ActivityExecutionContext that provides the reason for cancellation token being set.

Specific Changes

2025-04-28 - 98db10f - Add CODEOWNERS (#​467)
2025-04-28 - d48377d - Handle errors with update result serialization (#​468)
2025-04-28 - dcf7e1c - Replace BuildJet in build-binary smoke test (#​469)
2025-05-08 - 1890573 - Fail the workflow task if a requested local activity is not registered (#​472)
2025-05-14 - 4205a59 - Expose poller automation (#​477)
2025-05-14 - cbf20f9 - Worker Deployment Versioning (#​466)
2025-05-16 - 910fb1c - Improve/verbosify error messages in various ToInteropOptions methods (#​481)
2025-05-19 - 8918a31 - Properly restore auto-time-skipping after disabled (#​475)
2025-05-19 - b94084b - Add WorkflowInfo.WorkflowStartTime (#​476)
2025-05-27 - 864e654 - Activity pause support (#​482)
2025-05-29 - fa93167 - Added Category to ApplicationFailureException (#​483)
2025-06-06 - 761465d - Updated sdk-core to latest (#​485)
2025-06-06 - a7ca5ec - Make static summary/details lazy on workflow description (#​486)

Commits viewable in compare view.

Updated Temporalio.Extensions.OpenTelemetry from 1.6.0 to 1.9.0.

Release notes

Sourced from Temporalio.Extensions.OpenTelemetry's releases.

1.9.0

Get from NuGet and read the README

Highlights

Environment Configuration Support (experimental)

Users can now use Temporalio.Client.EnvConfig.ClientEnvConfig to 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.

⚠️ This is experimental and subject to change.

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 Nexus SDK README, the Temporal SDK README section, and the initial Nexus .NET sample.

⚠️ This is experimental and subject to change.

💥 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.AssertProtoPayload not 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.dll on Windows, libtemporal_sdk_bridge.so on Linux, and libtemporal_sdk_bridge.dylib on macOS.

The filename has changed to temporal_sdk_core_c_bridge.dll on Windows, libtemporal_sdk_core_c_bridge.so on Linux, and libtemporal_sdk_core_c_bridge.dylib on 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 after Dispose() (#​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)

1.7.0

Get from NuGet and read the README

Highlights

Workflow & Activity Priorities

Users can now set a priority key when scheduling a workflow, activity or child workflows. The priority key will be used to help prioritize certain tasks over others when there is a backlog. Priority is currently not supported in any OSS Temporal release, but support will be coming soon. To experiment with this feature please see the pre-release development server or if you are a Temporal Cloud customer reach out to your SA.

Worker deployment versioning preview

This release introduces a preview of new APIs that gracefully manage code changes and worker pools that support them. The goal is to better control which workers should execute new, and existing, workflows and activities tasks, based on their code and configuration.

VersioningBehavior.AutoUpgrade and VersioningBehavior.Pinned are two Versioning Behaviors that can be specified on a workflow implementation using the VersioningBehavior argument to the Workflow attribute. Pinned workflows are typically short lived, and are never affected by new versions, i.e., they do not need to use the patch API for compatibility. AutoUpgrade workflows are mostly long running, but they need to use patching to safely transition to new versions. The choice of Pinned vs AutoUpgrade ultimately depends on your willingness to keep old worker fleets running vs the complexity of patching.

To manage Worker Deployments please use the Temporal CLI, or Temporalio.Client.WorkflowService

Automatic Poller Scaling

You can configure Workers to automatically adjust the number of concurrent polls they make for tasks! Set the WorkflowTaskPollerBehavior and ActivityTaskPollerBehavior arguments of the Worker options to PollerBehavior.Autoscaling to try it out. You can expect fewer unnecessary polls during low load, and increased polls during high load when they can be used to increase task throughput.

Activity pause support

Activity pausing (not GA currently) will now cancel the activity cancellation token thereby interrupting activity execution similar to how activity cancel and worker shut down does. There is a new CancellationDetails property on the ActivityExecutionContext that provides the reason for cancellation token being set.

Specific Changes

2025-04-28 - 98db10f - Add CODEOWNERS (#​467)
2025-04-28 - d48377d - Handle errors with update result serialization (#​468)
2025-04-28 - dcf7e1c - Replace BuildJet in build-binary smoke test (#​469)
2025-05-08 - 1890573 - Fail the workflow task if a requested local activity is not registered (#​472)
2025-05-14 - 4205a59 - Expose poller automation (#​477)
2025-05-14 - cbf20f9 - Worker Deployment Versioning (#​466)
2025-05-16 - 910fb1c - Improve/verbosify error messages in various ToInteropOptions methods (#​481)
2025-05-19 - 8918a31 - Properly restore auto-time-skipping after disabled (#​475)
2025-05-19 - b94084b - Add WorkflowInfo.WorkflowStartTime (#​476)
2025-05-27 - 864e654 - Activity pause support (#​482)
2025-05-29 - fa93167 - Added Category to ApplicationFailureException (#​483)
2025-06-06 - 761465d - Updated sdk-core to latest (#​485)
2025-06-06 - a7ca5ec - Make static summary/details lazy on workflow description (#​486)

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
Bump the temporal group with 4 updates
e82b408 
Bumps Temporalio from 1.6.0 to 1.9.0
Bumps Temporalio.Extensions.DiagnosticSource from 1.6.0 to 1.9.0
Bumps Temporalio.Extensions.Hosting from 1.6.0 to 1.9.0
Bumps Temporalio.Extensions.OpenTelemetry from 1.6.0 to 1.9.0

---
updated-dependencies:
- dependency-name: Temporalio
  dependency-version: 1.9.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: temporal
- dependency-name: Temporalio.Extensions.DiagnosticSource
  dependency-version: 1.9.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: temporal
- dependency-name: Temporalio.Extensions.Hosting
  dependency-version: 1.9.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: temporal
- dependency-name: Temporalio.Extensions.OpenTelemetry
  dependency-version: 1.9.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: temporal
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Dependency update minor Minor changes labels Oct 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Dependency update minor Minor changes
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants