Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 21, 2025

Bumps the temporal group with 5 updates in the / directory:

Package From To
Temporalio 1.3.1 1.5.0
Microsoft.Extensions.DependencyInjection.Abstractions 8.0.1 8.0.2
Microsoft.Extensions.Hosting 8.0.0 8.0.1
Temporalio 1.3.1 1.5.0
Temporalio.Extensions.Hosting 1.3.1 1.5.0
Temporalio 1.3.1 1.5.0
Temporalio.Extensions.DiagnosticSource 1.3.1 1.5.0

Updates Temporalio from 1.3.1 to 1.5.0

Release notes

Sourced from Temporalio's releases.

1.5.0

Get from NuGet and read the README

Highlights

Search Attributes in Dev Server

To make testing easier, Temporalio.Testing.WorkflowEnvironment.StartLocalAsync now accepts SearchAttributes in its options to start the server with pre-created search attributes.

Client in Activity

It is a common use case to use a Temporal client in an activity. TemporalClient is now available on the Temporalio.Activities.ActivityExecutionContext to make this easier.

Activity Service Scope

For those using dependency injection, Temporalio.Extensions.Hosting.ActivityScope is now available which provides access to both the activity instance and IServiceScope to have access to the service provider in the activity or activity interceptor.

Specific Changes

2025-01-16 - 3dd6cca - Expose instance to workflows/activities and client to activities (#393) 2025-01-24 - b5ca854 - Accept search attributes for dev server (#289) 2025-02-03 - 69dfe5a - Updated the docs for IdReusePolicy property (#397) 2025-02-03 - 7b92674 - Fix issue where null timer summary breaks codec (#405) 2025-02-05 - 139a853 - Update Core & add HTTP Otel / Dev UI Port (#407) 2025-02-11 - 2b97703 - Document CA issues in AWS and Azure (#411) 2025-02-11 - f2ba7dd - Reserve __temporal prefix (#410)

1.4.0

Get from NuGet and read the README

Highlights

Custom Slot Suppliers in Worker Tuners (experimental)

Worker tuners can now be created with custom slot suppliers. By providing a class extending Temporalio.Worker.Tuning.CustomSlotSupplier to a worker tuner, users can now control logic of when slots are available for use by the worker. This allows advanced, dynamic control over in-process tuning for how many concurrent activities, local activities, and workflow tasks can run. This is an advanced feature and is currently experimental which means future releases can technically update the API in incompatible ways.

User Metadata (experimental)

When starting workflows (directly, via update with start, via schedules, or via child workflows), users can now set a StaticSummary and/or StaticDetails option which may appear in the UI/CLI in the future. Similarly, users can provide Summary to timers and activity invocations. Finally, users can set the Workflow.CurrentDetails property to a string that can updated be throughout the life of the workflow based on the workflow's state. This value may also appear in the UI/CLI in the future. Values for summary or details can be in limited single-line or multi-line markdown format, respectively. This feature is currently experimental which means future releases can technically update the API in incompatible ways.

Update with Start Workflow (experimental)

Users can use StartUpdateWithStartWorkflowAsync or ExecuteUpdateWithStartWorkflowAsync on newer servers to perform an update with start. An update with start first starts a workflow if it does not exist (subject to conflict policy), and regardless of whether it started a workflow or not, sends an update. Depending on the call made, it either waits for the update to reach the worker/workflow, or waits for the update to complete. This is a very useful feature for those wanting to start a workflow and get back an early programmatic result but still let the rest of the workflow continue in the background. This feature is currently experimental which means future releases can technically update the API in incompatible ways.

Workflow Update No Longer Experimental

The "experimental" label has been removed from workflow update and it is no longer considered experimental.

Specific Changes

... (truncated)

Commits

Updates Microsoft.Extensions.DependencyInjection.Abstractions from 8.0.1 to 8.0.2

Release notes

Sourced from Microsoft.Extensions.DependencyInjection.Abstractions's releases.

.NET 8.0.2

Release

Commits
  • 1381d5e Merge in 'release/8.0' changes
  • c987e4f [release/8.0] Fix Options Source Gen RangeAttribute Thread Safety (#97110)
  • 441c91d Merge in 'release/8.0' changes
  • c93800e Merge pull request #97065 from carlossanlop/release/8.0-staging
  • c2d2bb3 Merge branch 'release/8.0' into release/8.0-staging
  • 6d35e39 [release/8.0-staging] UInt64.CreateSaturating<Int128> truncates instead of sa...
  • 96b0a55 [release/8.0-staging] macOS: Set certificate as a dependency of private key h...
  • 85c2772 [release/8.0] Fix server-side OCSP stapling on Linux (#96838)
  • 683da71 [release/8.0-staging] Gen0 segment should always be reported as Gen0 for DacH...
  • f9d0a7b [release/8.0-staging] Fix Crossgen2 PDB generation (again) (#96566)
  • Additional commits viewable in compare view

Updates Microsoft.Extensions.Hosting from 8.0.0 to 8.0.1

Release notes

Sourced from Microsoft.Extensions.Hosting's releases.

.NET 8.0.1

Release

Commits
  • bf5e279 Merge in 'release/8.0' changes
  • a6e4834 [release/8.0] Free the tls memory on thread termination (#95439)
  • eddf880 Merge in 'release/8.0' changes
  • 89a2364 [release/8.0] Downgrade ServicingVersion for Microsoft.Extensions.Options to ...
  • d682195 Merge in 'release/8.0' changes
  • 8557ef2 Merge pull request #95148 from carlossanlop/release/8.0-staging
  • aaa4b27 Merge pull request #95082 from dotnet-maestro-bot/merge/release/8.0-to-releas...
  • 72e5ae9 X509Chain.Build should throw when an internal error occurs
  • a20ee6f [release/8.0-staging] Fix JsonArray.Add and ReplaceWith regressions. (#94882)
  • 4fc3df2 Fix incremental servicing condition (#95119)
  • Additional commits viewable in compare view

Updates Temporalio from 1.3.1 to 1.5.0

Release notes

Sourced from Temporalio's releases.

1.5.0

Get from NuGet and read the README

Highlights

Search Attributes in Dev Server

To make testing easier, Temporalio.Testing.WorkflowEnvironment.StartLocalAsync now accepts SearchAttributes in its options to start the server with pre-created search attributes.

Client in Activity

It is a common use case to use a Temporal client in an activity. TemporalClient is now available on the Temporalio.Activities.ActivityExecutionContext to make this easier.

Activity Service Scope

For those using dependency injection, Temporalio.Extensions.Hosting.ActivityScope is now available which provides access to both the activity instance and IServiceScope to have access to the service provider in the activity or activity interceptor.

Specific Changes

2025-01-16 - 3dd6cca - Expose instance to workflows/activities and client to activities (#393) 2025-01-24 - b5ca854 - Accept search attributes for dev server (#289) 2025-02-03 - 69dfe5a - Updated the docs for IdReusePolicy property (#397) 2025-02-03 - 7b92674 - Fix issue where null timer summary breaks codec (#405) 2025-02-05 - 139a853 - Update Core & add HTTP Otel / Dev UI Port (#407) 2025-02-11 - 2b97703 - Document CA issues in AWS and Azure (#411) 2025-02-11 - f2ba7dd - Reserve __temporal prefix (#410)

1.4.0

Get from NuGet and read the README

Highlights

Custom Slot Suppliers in Worker Tuners (experimental)

Worker tuners can now be created with custom slot suppliers. By providing a class extending Temporalio.Worker.Tuning.CustomSlotSupplier to a worker tuner, users can now control logic of when slots are available for use by the worker. This allows advanced, dynamic control over in-process tuning for how many concurrent activities, local activities, and workflow tasks can run. This is an advanced feature and is currently experimental which means future releases can technically update the API in incompatible ways.

User Metadata (experimental)

When starting workflows (directly, via update with start, via schedules, or via child workflows), users can now set a StaticSummary and/or StaticDetails option which may appear in the UI/CLI in the future. Similarly, users can provide Summary to timers and activity invocations. Finally, users can set the Workflow.CurrentDetails property to a string that can updated be throughout the life of the workflow based on the workflow's state. This value may also appear in the UI/CLI in the future. Values for summary or details can be in limited single-line or multi-line markdown format, respectively. This feature is currently experimental which means future releases can technically update the API in incompatible ways.

Update with Start Workflow (experimental)

Users can use StartUpdateWithStartWorkflowAsync or ExecuteUpdateWithStartWorkflowAsync on newer servers to perform an update with start. An update with start first starts a workflow if it does not exist (subject to conflict policy), and regardless of whether it started a workflow or not, sends an update. Depending on the call made, it either waits for the update to reach the worker/workflow, or waits for the update to complete. This is a very useful feature for those wanting to start a workflow and get back an early programmatic result but still let the rest of the workflow continue in the background. This feature is currently experimental which means future releases can technically update the API in incompatible ways.

Workflow Update No Longer Experimental

The "experimental" label has been removed from workflow update and it is no longer considered experimental.

Specific Changes

... (truncated)

Commits

Updates Temporalio.Extensions.Hosting from 1.3.1 to 1.5.0

Release notes

Sourced from Temporalio.Extensions.Hosting's releases.

1.5.0

Get from NuGet and read the README

Highlights

Search Attributes in Dev Server

To make testing easier, Temporalio.Testing.WorkflowEnvironment.StartLocalAsync now accepts SearchAttributes in its options to start the server with pre-created search attributes.

Client in Activity

It is a common use case to use a Temporal client in an activity. TemporalClient is now available on the Temporalio.Activities.ActivityExecutionContext to make this easier.

Activity Service Scope

For those using dependency injection, Temporalio.Extensions.Hosting.ActivityScope is now available which provides access to both the activity instance and IServiceScope to have access to the service provider in the activity or activity interceptor.

Specific Changes

2025-01-16 - 3dd6cca - Expose instance to workflows/activities and client to activities (#393) 2025-01-24 - b5ca854 - Accept search attributes for dev server (#289) 2025-02-03 - 69dfe5a - Updated the docs for IdReusePolicy property (#397) 2025-02-03 - 7b92674 - Fix issue where null timer summary breaks codec (#405) 2025-02-05 - 139a853 - Update Core & add HTTP Otel / Dev UI Port (#407) 2025-02-11 - 2b97703 - Document CA issues in AWS and Azure (#411) 2025-02-11 - f2ba7dd - Reserve __temporal prefix (#410)

1.4.0

Get from NuGet and read the README

Highlights

Custom Slot Suppliers in Worker Tuners (experimental)

Worker tuners can now be created with custom slot suppliers. By providing a class extending Temporalio.Worker.Tuning.CustomSlotSupplier to a worker tuner, users can now control logic of when slots are available for use by the worker. This allows advanced, dynamic control over in-process tuning for how many concurrent activities, local activities, and workflow tasks can run. This is an advanced feature and is currently experimental which means future releases can technically update the API in incompatible ways.

User Metadata (experimental)

When starting workflows (directly, via update with start, via schedules, or via child workflows), users can now set a StaticSummary and/or StaticDetails option which may appear in the UI/CLI in the future. Similarly, users can provide Summary to timers and activity invocations. Finally, users can set the Workflow.CurrentDetails property to a string that can updated be throughout the life of the workflow based on the workflow's state. This value may also appear in the UI/CLI in the future. Values for summary or details can be in limited single-line or multi-line markdown format, respectively. This feature is currently experimental which means future releases can technically update the API in incompatible ways.

Update with Start Workflow (experimental)

Users can use StartUpdateWithStartWorkflowAsync or ExecuteUpdateWithStartWorkflowAsync on newer servers to perform an update with start. An update with start first starts a workflow if it does not exist (subject to conflict policy), and regardless of whether it started a workflow or not, sends an update. Depending on the call made, it either waits for the update to reach the worker/workflow, or waits for the update to complete. This is a very useful feature for those wanting to start a workflow and get back an early programmatic result but still let the rest of the workflow continue in the background. This feature is currently experimental which means future releases can technically update the API in incompatible ways.

Workflow Update No Longer Experimental

The "experimental" label has been removed from workflow update and it is no longer considered experimental.

Specific Changes

... (truncated)

Commits

Updates Temporalio from 1.3.1 to 1.5.0

Release notes

Sourced from Temporalio's releases.

1.5.0

Get from NuGet and read the README

Highlights

Search Attributes in Dev Server

To make testing easier, Temporalio.Testing.WorkflowEnvironment.StartLocalAsync now accepts SearchAttributes in its options to start the server with pre-created search attributes.

Client in Activity

It is a common use case to use a Temporal client in an activity. TemporalClient is now available on the Temporalio.Activities.ActivityExecutionContext to make this easier.

Activity Service Scope

For those using dependency injection, Temporalio.Extensions.Hosting.ActivityScope is now available which provides access to both the activity instance and IServiceScope to have access to the service provider in the activity or activity interceptor.

Specific Changes

2025-01-16 - 3dd6cca - Expose instance to workflows/activities and client to activities (#393) 2025-01-24 - b5ca854 - Accept search attributes for dev server (#289) 2025-02-03 - 69dfe5a - Updated the docs for IdReusePolicy property (#397) 2025-02-03 - 7b92674 - Fix issue where null timer summary breaks codec (#405) 2025-02-05 - 139a853 - Update Core & add HTTP Otel / Dev UI Port (#407) 2025-02-11 - 2b97703 - Document CA issues in AWS and Azure (#411) 2025-02-11 - f2ba7dd - Reserve __temporal prefix (#410)

1.4.0

Get from NuGet and read the README

Highlights

Custom Slot Suppliers in Worker Tuners (experimental)

Worker tuners can now be created with custom slot suppliers. By providing a class extending Temporalio.Worker.Tuning.CustomSlotSupplier to a worker tuner, users can now control logic of when slots are available for use by the worker. This allows advanced, dynamic control over in-process tuning for how many concurrent activities, local activities, and workflow tasks can run. This is an advanced feature and is currently experimental which means future releases can technically update the API in incompatible ways.

User Metadata (experimental)

When starting workflows (directly, via update with start, via schedules, or via child workflows), users can now set a StaticSummary and/or StaticDetails option which may appear in the UI/CLI in the future. Similarly, users can provide Summary to timers and activity invocations. Finally, users can set the Workflow.CurrentDetails property to a string that can updated be throughout the life of the workflow based on the workflow's state. This value may also appear in the UI/CLI in the future. Values for summary or details can be in limited single-line or multi-line markdown format, respectively. This feature is currently experimental which means future releases can technically update the API in incompatible ways.

Update with Start Workflow (experimental)

Users can use StartUpdateWithStartWorkflowAsync or ExecuteUpdateWithStartWorkflowAsync on newer servers to perform an update with start. An update with start first starts a workflow if it does not exist (subject to conflict policy), and regardless of whether it started a workflow or not, sends an update. Depending on the call made, it either waits for the update to reach the worker/workflow, or waits for the update to complete. This is a very useful feature for those wanting to start a workflow and get back an early programmatic result but still let the rest of the workflow continue in the background. This feature is currently experimental which means future releases can technically update the API in incompatible ways.

Workflow Update No Longer Experimental

The "experimental" label has been removed from workflow update and it is no longer considered experimental.

Specific Changes

... (truncated)

Commits

Updates Temporalio.Extensions.DiagnosticSource from 1.3.1 to 1.5.0

Release notes

Sourced from Temporalio.Extensions.DiagnosticSource's releases.

1.5.0

Get from NuGet and read the README

Highlights

Search Attributes in Dev Server

To make testing easier, Temporalio.Testing.WorkflowEnvironment.StartLocalAsync now accepts SearchAttributes in its options to start the server with pre-created search attributes.

Client in Activity

It is a common use case to use a Temporal client in an activity. TemporalClient is now available on the Temporalio.Activities.ActivityExecutionContext to make this easier.

Activity Service Scope

For those using dependency injection, Temporalio.Extensions.Hosting.ActivityScope is now available which provides access to both the activity instance and IServiceScope to have access to the service provider in the activity or activity interceptor.

Specific Changes

2025-01-16 - 3dd6cca - Expose instance to workflows/activities and client to activities (#393) 2025-01-24 - b5ca854 - Accept search attributes for dev server (#289) 2025-02-03 - 69dfe5a - Updated the docs for IdReusePolicy property (#397) 2025-02-03 - 7b92674 - Fix issue where null timer summary breaks codec (#405) 2025-02-05 - 139a853 - Update Core & add HTTP Otel / Dev UI Port (#407) 2025-02-11 - 2b97703 - Document CA issues in AWS and Azure (#411) 2025-02-11 - f2ba7dd - Reserve __temporal prefix (#410)

1.4.0

Get from NuGet and read the README

Highlights

Custom Slot Suppliers in Worker Tuners (experimental)

Worker tuners can now be created with custom slot suppliers. By providing a class extending Temporalio.Worker.Tuning.CustomSlotSupplier to a worker tuner, users can now control logic of when slots are available for use by the worker. This allows advanced, dynamic control over in-process tuning for how many concurrent activities, local activities, and workflow tasks can run. This is an advanced feature and is currently experimental which means future releases can technically update the API in incompatible ways.

User Metadata (experimental)

When starting workflows (directly, via update with start, via schedules, or via child workflows), users can now set a StaticSummary and/or StaticDetails option which may appear in the UI/CLI in the future. Similarly, users can provide Summary to timers and activity invocations. Finally, users can set the Workflow.CurrentDetails property to a string that can updated be throughout the life of the workflow based on the workflow's state. This value may also appear in the UI/CLI in the future. Values for summary or details can be in limited single-line or multi-line markdown format, respectively. This feature is currently experimental which means future releases can technically update the API in incompatible ways.

Update with Start Workflow (experimental)

Users can use StartUpdateWithStartWorkflowAsync or ExecuteUpdateWithStartWorkflowAsync on newer servers to perform an update with start. An update with start first starts a workflow if it does not exist (subject to conflict policy), and regardless of whether it started a workflow or not, sends an update. Depending on the call made, it either waits for the update to reach the worker/workflow, or waits for the update to complete. This is a very useful feature for those wanting to start a workflow and get back an early programmatic result but still let the rest of the workflow continue in the background. This feature is currently experimental which means future releases can technically update the API in incompatible ways.

Workflow Update No Longer Experimental

The "experimental" label has been removed from workflow update and it is no longer considered experimental.

Specific Changes

... (truncated)

Commits

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

Bumps the temporal group with 5 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [Temporalio](https://github.com/temporalio/sdk-dotnet) | `1.3.1` | `1.5.0` |
| [Microsoft.Extensions.DependencyInjection.Abstractions](https://github.com/dotnet/runtime) | `8.0.1` | `8.0.2` |
| [Microsoft.Extensions.Hosting](https://github.com/dotnet/runtime) | `8.0.0` | `8.0.1` |
| [Temporalio](https://github.com/temporalio/sdk-dotnet) | `1.3.1` | `1.5.0` |
| [Temporalio.Extensions.Hosting](https://github.com/temporalio/sdk-dotnet) | `1.3.1` | `1.5.0` |
| [Temporalio](https://github.com/temporalio/sdk-dotnet) | `1.3.1` | `1.5.0` |
| [Temporalio.Extensions.DiagnosticSource](https://github.com/temporalio/sdk-dotnet) | `1.3.1` | `1.5.0` |



Updates `Temporalio` from 1.3.1 to 1.5.0
- [Release notes](https://github.com/temporalio/sdk-dotnet/releases)
- [Commits](temporalio/sdk-dotnet@1.3.1...1.5.0)

Updates `Microsoft.Extensions.DependencyInjection.Abstractions` from 8.0.1 to 8.0.2
- [Release notes](https://github.com/dotnet/runtime/releases)
- [Commits](dotnet/runtime@v8.0.1...v8.0.2)

Updates `Microsoft.Extensions.Hosting` from 8.0.0 to 8.0.1
- [Release notes](https://github.com/dotnet/runtime/releases)
- [Commits](dotnet/runtime@v8.0.0...v8.0.1)

Updates `Temporalio` from 1.3.1 to 1.5.0
- [Release notes](https://github.com/temporalio/sdk-dotnet/releases)
- [Commits](temporalio/sdk-dotnet@1.3.1...1.5.0)

Updates `Temporalio.Extensions.Hosting` from 1.3.1 to 1.5.0
- [Release notes](https://github.com/temporalio/sdk-dotnet/releases)
- [Commits](temporalio/sdk-dotnet@1.3.1...1.5.0)

Updates `Temporalio` from 1.3.1 to 1.5.0
- [Release notes](https://github.com/temporalio/sdk-dotnet/releases)
- [Commits](temporalio/sdk-dotnet@1.3.1...1.5.0)

Updates `Temporalio.Extensions.DiagnosticSource` from 1.3.1 to 1.5.0
- [Release notes](https://github.com/temporalio/sdk-dotnet/releases)
- [Commits](temporalio/sdk-dotnet@1.3.1...1.5.0)

---
updated-dependencies:
- dependency-name: Temporalio
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: temporal
- dependency-name: Microsoft.Extensions.DependencyInjection.Abstractions
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: temporal
- dependency-name: Microsoft.Extensions.Hosting
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: temporal
- dependency-name: Temporalio
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: temporal
- dependency-name: Temporalio.Extensions.Hosting
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: temporal
- dependency-name: Temporalio
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: temporal
- dependency-name: Temporalio.Extensions.DiagnosticSource
  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 Feb 21, 2025
@ElanHasson ElanHasson merged commit 0ceaaf7 into main Feb 21, 2025
3 checks passed
@ElanHasson ElanHasson deleted the dependabot/nuget/temporal-1f8923c3e6 branch February 21, 2025 14:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Dependency update minor Minor changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants