Skip to content

Bump the elsa group with 4 updates#1324

Merged
github-actions[bot] merged 1 commit intomasterfrom
dependabot/nuget/Elsademo/ElsaCore.Server/elsa-61cc1c1380
Mar 5, 2026
Merged

Bump the elsa group with 4 updates#1324
github-actions[bot] merged 1 commit intomasterfrom
dependabot/nuget/Elsademo/ElsaCore.Server/elsa-61cc1c1380

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 5, 2026

Updated Elsa from 3.5.3 to 3.6.0.

Release notes

Sourced from Elsa's releases.

3.6.0

Elsa 3.6.0 — Release Notes

Compare: 3.5.3...3.6.0

⚠️ Breaking changes / upgrade notes

  • Database migrations (EF Core — all providers): ActivityNodeId columns in ActivityExecutionRecords and WorkflowExecutionLogRecords have been widened to unlimited types (nvarchar(max) / longtext / NCLOB) to support deeply nested workflows. The corresponding B-tree indexes (IX_ActivityExecutionRecord_ActivityNodeId, IX_WorkflowExecutionLogRecord_ActivityNodeId) are dropped as part of the V3_6 migrations. You must apply the EF Core migrations before upgrading to 3.6.0 in any SQL Server, MySQL, or Oracle deployment. (d4b69be44b) (#​7338)

  • Multitenancy — tenant ID convention change: An empty string ("") is now the canonical default tenant ID for all tenant-aware entities; null now means tenant-agnostic (visible to all tenants). EF Core query filters and the ActivityRegistry have been updated accordingly. If your database contains rows with a null TenantId that were intended to represent the default tenant, migrate those rows to "" before upgrading. The new NormalizeTenantId() extension method on string handles the conversion in code. (#​7217, #​7226)

  • Multitenancy — stored-trigger index updated: Database indexes on stored triggers now include TenantId. The V3_6 migration adds this index; no manual action is required beyond running migrations. (#​7217)

  • DefaultRegistriesPopulator constructor change: The constructor now requires an additional INotificationSender dependency. If you manually instantiate or override DefaultRegistriesPopulator in tests or custom DI registrations, add the new parameter. Standard DI consumers are unaffected. (#​7293)

  • Elsa.Common dependency trimmed: The DistributedLock meta-package (which pulled in all provider implementations) has been replaced with DistributedLock.Core. Applications that relied on the transitive provider packages (e.g. DistributedLock.SqlServer) being pulled in via Elsa.Common must add explicit package references. (53245cafbd) (#​7169)

✨ New features

Activity host registration

  • HostMethodActivity / activity hosts: Introduces support for registering CLR types as activity hosts. Public async methods on a registered type are automatically discovered and exposed as individual activities in the workflow designer, enabling code-first activity generation without manual activity boilerplate. New types: HostMethodActivity, HostMethodActivityProvider, IHostMethodActivityDescriber, FromServicesAttribute. (fa04e1ebcd) (#​7172)

Workflow dispatch notifications

  • Dispatch lifecycle notifications: BackgroundWorkflowDispatcher now emits four new notifications at dispatch time, allowing subscribers to react to durable dispatch scenarios without a custom dispatcher:

    • WorkflowDefinitionDispatching / WorkflowDefinitionDispatched
    • WorkflowInstanceDispatching / WorkflowInstanceDispatched

    (411ca0a332) (#​7157)

  • WorkflowDefinitionsReloaded notification: DefaultRegistriesPopulator now dispatches a WorkflowDefinitionsReloaded notification after repopulating the workflow definition store, enabling subscriber nodes to synchronize their registries. (f5505d66c9) (#​7293)

Consumers API & recursive export

  • GET /workflow-definitions/{definitionId}/consumers: New endpoint returns all recursive consuming workflow definitions for a given definition. Built on a new IWorkflowReferenceGraphBuilder / WorkflowReferenceGraph model that replaces the previous ad-hoc recursive query approach. (0a2e99ad42) (#​7309)

  • Export with transitive consumers: The export endpoint and BulkExportWorkflowDefinitionsRequest now accept an IncludeConsumingWorkflows flag (default false). When enabled, the ZIP export recursively resolves and includes all consuming workflows at their latest version. Exported filenames are now deterministic ({Name}-{DefinitionId}.json). (0a2e99ad42) (#​7309)

Default commit strategies

  • Global default commit strategies: New WithDefaultWorkflowCommitStrategy() and WithDefaultActivityCommitStrategy() extension methods on the workflows builder let you set application-wide fallback commit strategies. The resolution order for activities is: activity-specific → default activity → workflow-specific → default workflow → no commit. Default strategies are stored separately from the registry so they don't appear in the UI/tooling. (31eff52d24) (#​7148)

Multitenancy enhancements

  • Null TenantId for tenant-agnostic entities: Entities with a null TenantId are now treated as visible across all tenants. EF Core query filters and ActivityRegistry query methods include null-tenanted records in every tenant's scope. New ActivityDescriptor.TenantId (nullable) property added. (7bc9035f5e) (#​7226)

... (truncated)

3.6.0-rc5

What's Changed

Full Changelog: elsa-workflows/elsa-core@3.6.0-rc4...3.6.0-rc5

3.6.0-rc4

What's Changed

Full Changelog: elsa-workflows/elsa-core@3.6.0-rc3...3.6.0-rc4

3.6.0-rc3

Compare: 3.6.0-rc2...3.6.0-rc3

This release candidate includes significant multitenancy improvements, bug fixes, and enhanced test coverage.

⚠️ Breaking changes / upgrade notes

Multitenancy Tenant ID Convention Changes

Affected users: Applications using multitenancy features, especially those with existing tenant data.

What changed:

  • Default tenant ID convention: The default tenant now uses an empty string ("") instead of null (ADR-0008). (b09a56481) (#​7217)
  • Tenant-agnostic entity convention: Tenant-agnostic entities (visible to all tenants) now use asterisk ("*") as the sentinel value instead of null (ADR-0009). (7bc9035f5) (#​7226)
  • Database schema impact: Database indexes on the Triggers table now include TenantId in unique constraints across all EF Core providers. (b09a56481) (#​7217)

Migration required:

  • Convert existing null TenantId values to empty strings for default tenant data in WorkflowDefinitions, WorkflowInstances, and runtime entities.
  • Review ADR-0008 (Default Tenant ID) and ADR-0009 (Tenant-Agnostic Entities) in doc/adr/ for detailed rationale and migration guidance.

Query filter changes: EF Core query filters have been updated to handle the new tenant ID conventions, ensuring tenant isolation is properly maintained. (7bc9035f5) (#​7226)

✨ New features

Multitenancy enhancements

  • Configuration-based multitenancy: Introduced configuration-based tenant provider to streamline tenant initialization and customization. (b09a56481) (#​7217)
  • Tenant-agnostic workflow support: Workflows and activities can now be marked as tenant-agnostic (using "*" as tenant ID) to make them accessible across all tenants. (7bc9035f5) (#​7226)
  • Selective lock mocking in tests: Added SelectiveMockLockProvider for precise lock mocking in tests without affecting unrelated background operations. (b09a56481) (#​7217)

🔧 Improvements

Multitenancy

  • Tenant filtering in workflow store populator: Added tenant-specific filtering in DefaultWorkflowDefinitionStorePopulator to ensure workflows are only loaded for the current tenant. (b09a56481) (#​7217)
  • Tenant isolation in activity provider: Enforced tenant isolation in WorkflowDefinitionActivityProvider and included tenant ID in activity type names for better separation. (558902bb7)
  • Optimized activity registry: Improved ActivityRegistry.Find to prefer tenant-specific descriptors over tenant-agnostic ones with single-pass iteration for better performance. (7bc9035f5) (#​7226)
  • Tenant headers support: Added tenant headers support to BackgroundWorkflowCancellationDispatcher for proper tenant context propagation during workflow cancellation. (bc70beff1) (#​7040)

API improvements

  • Labels endpoints migration: Updated Labels endpoints to use ElsaEndpoint base class with standardized permission configuration. (72569702f) (#​7205)

Error handling

... (truncated)

3.6.0-rc2

Compare: 3.6.0-rc1...3.6.0-rc2

⚠️ Breaking changes / upgrade notes

  • CI / SDK: GitHub workflow now uses .NET SDK 10.x (was 9.x). (b22956c792) (fa2254f41b) (72597f733f)
  • Bookmarks model change: Bookmark moved from a positional record to a mutable class (serialization/back-compat oriented). (ca268c16ad) (#​7161)
  • DistributedLock package: Elsa.Common now references DistributedLock.Core instead of DistributedLock. (#​7169)

✨ New features

Activity hosts / host-method activities

  • Introduced host-method activities: expose public methods on configured CLR types as workflow activities. (#​7172)
    • Parameter binding extensibility (e.g. DI-backed parameters using [FromServices]). (#​7172)
  • Added a sample activity host (Penguin) and registered it in Elsa.Server.Web. (#​7172)

Commit strategies (defaults)

  • Added support for global default commit strategies (fallback when no explicit strategy is configured). (#​7148)

Resilience / transient exception detection

  • Added transient exception detection infrastructure and registration. (ca268c16ad) (#​7161)

Workflow dispatch notifications

  • Added new notifications emitted by the background dispatcher. (#​7157)

Tenant task lifecycle & dependencies

  • Introduced TenantTaskManager and dependency ordering support ([TaskDependency], TopologicalTaskSorter). (#​7174)

🔧 Improvements

  • Distributed runtime lock resilience: Polly retry around distributed lock acquisition (with transient exception detection), and safer lock release behavior. (#​7161)
  • Mediator background services: improved cancellation handling to avoid noisy failures. (ca268c16ad) (#​7161)
  • Xunit logging: suppress “no currently active test” errors from late background log writes. (ca268c16ad) (#​7161)
  • Small cleanups:
    • Make correlationId parameter non-optional in WorkflowExecutionContext constructor. (fa798b0a47)
    • Remove unused ClearCompletionCallbacks from WorkflowExecutionContext. (79a64e90fd)

🐛 Fixes

  • Literal inputs: ActivityExecutionContext.TryGet(...) correctly handles Literal references by returning the literal’s value directly. (#​7075)

🧩 Developer-facing changes

  • Attribute usage expanded:
    • ActivityAttribute: now valid on classes, interfaces, and methods. (3778a14e54)
    • InputAttribute: now valid on properties and parameters. (3778a14e54)
    • OutputAttribute: now valid on properties, classes, methods, and return values. (3778a14e54)

🧪 Tests

  • Added/expanded coverage for:
    • Host method activity registration & descriptor behavior. (#​7172)
    • Distributed lock resilience (acquisition retries + release failure behavior). (#​7161)
    • Literal input handling. (#​7075)
    • Default workflow/activity commit strategy behavior. (#​7148)
    • Workflow dispatch notifications. (#​7157)
    • Tenant task dependency ordering / topological sorting. (#​7174)
      ... (truncated)

3.6.0-rc1

Elsa Workflows 3.6.0 RC1

This release focuses on Flowchart execution improvements, stronger runtime correctness, major test coverage expansion, reliability fixes for scheduling/triggers and HTTP content handling, and a platform upgrade to .NET 10 while retaining support for .NET 8 and .NET 9.

Highlights

  • Token-centric Flowchart execution model with configurable MergeMode, plus multiple refinements and DI-based configuration (opt-in). See Flowchart: token-based execution + per-activity MergeMode. (PRs: #​6632, #​6937, #​6993, #​7141)
  • Upgrade to .NET 10 across the solution (with conditional compatibility dependencies where needed). (PR: #​7062)
  • New Activity Testing API and a major expansion of unit/integration/component test coverage across core activities, scheduling, HTTP endpoints, JavaScript, and flowchart execution. (PR: #​6719 and many follow-ups)
  • Improved runtime observability & execution record serialization, including snapshots and a new ActivityCompleted notification. (PRs: #​6675, #​6800, #​6807)
  • Reliability fixes across triggers/scheduling and HTTP content handling (cron delay edge cases, multi-engine trigger registration, Content-Length / charset issues). (PRs: #​7047, #​7131, #​6676, #​7027)

Flowchart: token-based execution + per-activity MergeMode (opt-in)

Elsa 3.6.0 introduces an optional token-based execution algorithm for the Flowchart activity. Instead of relying on the previous counter-based scheduling model, the Flowchart can now track progress using tokens that represent a taken connection (from a source activity outcome to a target activity).

When an activity completes, the flowchart:

  • Emits tokens for each taken outbound connection (based on the activity’s outcome names).
  • Consumes inbound tokens that were waiting for the completed activity.
  • Schedules downstream activities based on each target activity’s MergeMode.

New: MergeMode (configurable per activity)

With token-based execution enabled, Flowchart supports a new MergeMode concept that determines how a node behaves when it has multiple inbound connections. You can now specify a merge mode per activity, allowing different “join” semantics within the same flowchart.

In broad terms, merge modes enable behaviors like:

  • Stream-like behavior: proceeds without strict joining, helping avoid dead-path waiting.
  • Forward-join behavior (Merge): waits for tokens from all forward inbound connections (loop/back edges don’t block).
  • Strict join behavior (Converge): waits for tokens from all inbound connections, including loop/back edges.
  • First-arrival behavior (Cascade / Race): schedules on the first arriving inbound token; in Race mode, other inbound ancestors are canceled so only the “winning” path continues.

This improves predictability for joins, forks, and cyclic graphs, while giving you fine-grained control over how each activity merges incoming paths.

How to opt in (Program.cs)

Token-based Flowchart execution is opt-in. Enable it via the Flowchart feature configuration:

elsa.UseFlowchart(flowchart => flowchart.UseTokenBasedExecution())

Breaking / Upgrading Notes

These are the changes most likely to affect upgrades from 3.5.x.

1) Multi-targeting: .NET 8, .NET 9, and .NET 10

Elsa 3.6.0 multi-targets .NET 8, .NET 9, and .NET 10.

  • Most consumers can continue targeting .NET 8 or .NET 9.
    ... (truncated)

Commits viewable in compare view.

Updated Elsa.Identity from 3.5.3 to 3.6.0.

Release notes

Sourced from Elsa.Identity's releases.

3.6.0

Elsa 3.6.0 — Release Notes

Compare: 3.5.3...3.6.0

⚠️ Breaking changes / upgrade notes

  • Database migrations (EF Core — all providers): ActivityNodeId columns in ActivityExecutionRecords and WorkflowExecutionLogRecords have been widened to unlimited types (nvarchar(max) / longtext / NCLOB) to support deeply nested workflows. The corresponding B-tree indexes (IX_ActivityExecutionRecord_ActivityNodeId, IX_WorkflowExecutionLogRecord_ActivityNodeId) are dropped as part of the V3_6 migrations. You must apply the EF Core migrations before upgrading to 3.6.0 in any SQL Server, MySQL, or Oracle deployment. (d4b69be44b) (#​7338)

  • Multitenancy — tenant ID convention change: An empty string ("") is now the canonical default tenant ID for all tenant-aware entities; null now means tenant-agnostic (visible to all tenants). EF Core query filters and the ActivityRegistry have been updated accordingly. If your database contains rows with a null TenantId that were intended to represent the default tenant, migrate those rows to "" before upgrading. The new NormalizeTenantId() extension method on string handles the conversion in code. (#​7217, #​7226)

  • Multitenancy — stored-trigger index updated: Database indexes on stored triggers now include TenantId. The V3_6 migration adds this index; no manual action is required beyond running migrations. (#​7217)

  • DefaultRegistriesPopulator constructor change: The constructor now requires an additional INotificationSender dependency. If you manually instantiate or override DefaultRegistriesPopulator in tests or custom DI registrations, add the new parameter. Standard DI consumers are unaffected. (#​7293)

  • Elsa.Common dependency trimmed: The DistributedLock meta-package (which pulled in all provider implementations) has been replaced with DistributedLock.Core. Applications that relied on the transitive provider packages (e.g. DistributedLock.SqlServer) being pulled in via Elsa.Common must add explicit package references. (53245cafbd) (#​7169)

✨ New features

Activity host registration

  • HostMethodActivity / activity hosts: Introduces support for registering CLR types as activity hosts. Public async methods on a registered type are automatically discovered and exposed as individual activities in the workflow designer, enabling code-first activity generation without manual activity boilerplate. New types: HostMethodActivity, HostMethodActivityProvider, IHostMethodActivityDescriber, FromServicesAttribute. (fa04e1ebcd) (#​7172)

Workflow dispatch notifications

  • Dispatch lifecycle notifications: BackgroundWorkflowDispatcher now emits four new notifications at dispatch time, allowing subscribers to react to durable dispatch scenarios without a custom dispatcher:

    • WorkflowDefinitionDispatching / WorkflowDefinitionDispatched
    • WorkflowInstanceDispatching / WorkflowInstanceDispatched

    (411ca0a332) (#​7157)

  • WorkflowDefinitionsReloaded notification: DefaultRegistriesPopulator now dispatches a WorkflowDefinitionsReloaded notification after repopulating the workflow definition store, enabling subscriber nodes to synchronize their registries. (f5505d66c9) (#​7293)

Consumers API & recursive export

  • GET /workflow-definitions/{definitionId}/consumers: New endpoint returns all recursive consuming workflow definitions for a given definition. Built on a new IWorkflowReferenceGraphBuilder / WorkflowReferenceGraph model that replaces the previous ad-hoc recursive query approach. (0a2e99ad42) (#​7309)

  • Export with transitive consumers: The export endpoint and BulkExportWorkflowDefinitionsRequest now accept an IncludeConsumingWorkflows flag (default false). When enabled, the ZIP export recursively resolves and includes all consuming workflows at their latest version. Exported filenames are now deterministic ({Name}-{DefinitionId}.json). (0a2e99ad42) (#​7309)

Default commit strategies

  • Global default commit strategies: New WithDefaultWorkflowCommitStrategy() and WithDefaultActivityCommitStrategy() extension methods on the workflows builder let you set application-wide fallback commit strategies. The resolution order for activities is: activity-specific → default activity → workflow-specific → default workflow → no commit. Default strategies are stored separately from the registry so they don't appear in the UI/tooling. (31eff52d24) (#​7148)

Multitenancy enhancements

  • Null TenantId for tenant-agnostic entities: Entities with a null TenantId are now treated as visible across all tenants. EF Core query filters and ActivityRegistry query methods include null-tenanted records in every tenant's scope. New ActivityDescriptor.TenantId (nullable) property added. (7bc9035f5e) (#​7226)

... (truncated)

3.6.0-rc5

What's Changed

Full Changelog: elsa-workflows/elsa-core@3.6.0-rc4...3.6.0-rc5

3.6.0-rc4

What's Changed

Full Changelog: elsa-workflows/elsa-core@3.6.0-rc3...3.6.0-rc4

3.6.0-rc3

Compare: 3.6.0-rc2...3.6.0-rc3

This release candidate includes significant multitenancy improvements, bug fixes, and enhanced test coverage.

⚠️ Breaking changes / upgrade notes

Multitenancy Tenant ID Convention Changes

Affected users: Applications using multitenancy features, especially those with existing tenant data.

What changed:

  • Default tenant ID convention: The default tenant now uses an empty string ("") instead of null (ADR-0008). (b09a56481) (#​7217)
  • Tenant-agnostic entity convention: Tenant-agnostic entities (visible to all tenants) now use asterisk ("*") as the sentinel value instead of null (ADR-0009). (7bc9035f5) (#​7226)
  • Database schema impact: Database indexes on the Triggers table now include TenantId in unique constraints across all EF Core providers. (b09a56481) (#​7217)

Migration required:

  • Convert existing null TenantId values to empty strings for default tenant data in WorkflowDefinitions, WorkflowInstances, and runtime entities.
  • Review ADR-0008 (Default Tenant ID) and ADR-0009 (Tenant-Agnostic Entities) in doc/adr/ for detailed rationale and migration guidance.

Query filter changes: EF Core query filters have been updated to handle the new tenant ID conventions, ensuring tenant isolation is properly maintained. (7bc9035f5) (#​7226)

✨ New features

Multitenancy enhancements

  • Configuration-based multitenancy: Introduced configuration-based tenant provider to streamline tenant initialization and customization. (b09a56481) (#​7217)
  • Tenant-agnostic workflow support: Workflows and activities can now be marked as tenant-agnostic (using "*" as tenant ID) to make them accessible across all tenants. (7bc9035f5) (#​7226)
  • Selective lock mocking in tests: Added SelectiveMockLockProvider for precise lock mocking in tests without affecting unrelated background operations. (b09a56481) (#​7217)

🔧 Improvements

Multitenancy

  • Tenant filtering in workflow store populator: Added tenant-specific filtering in DefaultWorkflowDefinitionStorePopulator to ensure workflows are only loaded for the current tenant. (b09a56481) (#​7217)
  • Tenant isolation in activity provider: Enforced tenant isolation in WorkflowDefinitionActivityProvider and included tenant ID in activity type names for better separation. (558902bb7)
  • Optimized activity registry: Improved ActivityRegistry.Find to prefer tenant-specific descriptors over tenant-agnostic ones with single-pass iteration for better performance. (7bc9035f5) (#​7226)
  • Tenant headers support: Added tenant headers support to BackgroundWorkflowCancellationDispatcher for proper tenant context propagation during workflow cancellation. (bc70beff1) (#​7040)

API improvements

  • Labels endpoints migration: Updated Labels endpoints to use ElsaEndpoint base class with standardized permission configuration. (72569702f) (#​7205)

Error handling

... (truncated)

3.6.0-rc2

Compare: 3.6.0-rc1...3.6.0-rc2

⚠️ Breaking changes / upgrade notes

  • CI / SDK: GitHub workflow now uses .NET SDK 10.x (was 9.x). (b22956c792) (fa2254f41b) (72597f733f)
  • Bookmarks model change: Bookmark moved from a positional record to a mutable class (serialization/back-compat oriented). (ca268c16ad) (#​7161)
  • DistributedLock package: Elsa.Common now references DistributedLock.Core instead of DistributedLock. (#​7169)

✨ New features

Activity hosts / host-method activities

  • Introduced host-method activities: expose public methods on configured CLR types as workflow activities. (#​7172)
    • Parameter binding extensibility (e.g. DI-backed parameters using [FromServices]). (#​7172)
  • Added a sample activity host (Penguin) and registered it in Elsa.Server.Web. (#​7172)

Commit strategies (defaults)

  • Added support for global default commit strategies (fallback when no explicit strategy is configured). (#​7148)

Resilience / transient exception detection

  • Added transient exception detection infrastructure and registration. (ca268c16ad) (#​7161)

Workflow dispatch notifications

  • Added new notifications emitted by the background dispatcher. (#​7157)

Tenant task lifecycle & dependencies

  • Introduced TenantTaskManager and dependency ordering support ([TaskDependency], TopologicalTaskSorter). (#​7174)

🔧 Improvements

  • Distributed runtime lock resilience: Polly retry around distributed lock acquisition (with transient exception detection), and safer lock release behavior. (#​7161)
  • Mediator background services: improved cancellation handling to avoid noisy failures. (ca268c16ad) (#​7161)
  • Xunit logging: suppress “no currently active test” errors from late background log writes. (ca268c16ad) (#​7161)
  • Small cleanups:
    • Make correlationId parameter non-optional in WorkflowExecutionContext constructor. (fa798b0a47)
    • Remove unused ClearCompletionCallbacks from WorkflowExecutionContext. (79a64e90fd)

🐛 Fixes

  • Literal inputs: ActivityExecutionContext.TryGet(...) correctly handles Literal references by returning the literal’s value directly. (#​7075)

🧩 Developer-facing changes

  • Attribute usage expanded:
    • ActivityAttribute: now valid on classes, interfaces, and methods. (3778a14e54)
    • InputAttribute: now valid on properties and parameters. (3778a14e54)
    • OutputAttribute: now valid on properties, classes, methods, and return values. (3778a14e54)

🧪 Tests

  • Added/expanded coverage for:
    • Host method activity registration & descriptor behavior. (#​7172)
    • Distributed lock resilience (acquisition retries + release failure behavior). (#​7161)
    • Literal input handling. (#​7075)
    • Default workflow/activity commit strategy behavior. (#​7148)
    • Workflow dispatch notifications. (#​7157)
    • Tenant task dependency ordering / topological sorting. (#​7174)
      ... (truncated)

3.6.0-rc1

Elsa Workflows 3.6.0 RC1

This release focuses on Flowchart execution improvements, stronger runtime correctness, major test coverage expansion, reliability fixes for scheduling/triggers and HTTP content handling, and a platform upgrade to .NET 10 while retaining support for .NET 8 and .NET 9.

Highlights

  • Token-centric Flowchart execution model with configurable MergeMode, plus multiple refinements and DI-based configuration (opt-in). See Flowchart: token-based execution + per-activity MergeMode. (PRs: #​6632, #​6937, #​6993, #​7141)
  • Upgrade to .NET 10 across the solution (with conditional compatibility dependencies where needed). (PR: #​7062)
  • New Activity Testing API and a major expansion of unit/integration/component test coverage across core activities, scheduling, HTTP endpoints, JavaScript, and flowchart execution. (PR: #​6719 and many follow-ups)
  • Improved runtime observability & execution record serialization, including snapshots and a new ActivityCompleted notification. (PRs: #​6675, #​6800, #​6807)
  • Reliability fixes across triggers/scheduling and HTTP content handling (cron delay edge cases, multi-engine trigger registration, Content-Length / charset issues). (PRs: #​7047, #​7131, #​6676, #​7027)

Flowchart: token-based execution + per-activity MergeMode (opt-in)

Elsa 3.6.0 introduces an optional token-based execution algorithm for the Flowchart activity. Instead of relying on the previous counter-based scheduling model, the Flowchart can now track progress using tokens that represent a taken connection (from a source activity outcome to a target activity).

When an activity completes, the flowchart:

  • Emits tokens for each taken outbound connection (based on the activity’s outcome names).
  • Consumes inbound tokens that were waiting for the completed activity.
  • Schedules downstream activities based on each target activity’s MergeMode.

New: MergeMode (configurable per activity)

With token-based execution enabled, Flowchart supports a new MergeMode concept that determines how a node behaves when it has multiple inbound connections. You can now specify a merge mode per activity, allowing different “join” semantics within the same flowchart.

In broad terms, merge modes enable behaviors like:

  • Stream-like behavior: proceeds without strict joining, helping avoid dead-path waiting.
  • Forward-join behavior (Merge): waits for tokens from all forward inbound connections (loop/back edges don’t block).
  • Strict join behavior (Converge): waits for tokens from all inbound connections, including loop/back edges.
  • First-arrival behavior (Cascade / Race): schedules on the first arriving inbound token; in Race mode, other inbound ancestors are canceled so only the “winning” path continues.

This improves predictability for joins, forks, and cyclic graphs, while giving you fine-grained control over how each activity merges incoming paths.

How to opt in (Program.cs)

Token-based Flowchart execution is opt-in. Enable it via the Flowchart feature configuration:

elsa.UseFlowchart(flowchart => flowchart.UseTokenBasedExecution())

Breaking / Upgrading Notes

These are the changes most likely to affect upgrades from 3.5.x.

1) Multi-targeting: .NET 8, .NET 9, and .NET 10

Elsa 3.6.0 multi-targets .NET 8, .NET 9, and .NET 10.

  • Most consumers can continue targeting .NET 8 or .NET 9.
    ... (truncated)

Commits viewable in compare view.

Updated Elsa.Scheduling from 3.5.3 to 3.6.0.

Release notes

Sourced from Elsa.Scheduling's releases.

3.6.0

Elsa 3.6.0 — Release Notes

Compare: 3.5.3...3.6.0

⚠️ Breaking changes / upgrade notes

  • Database migrations (EF Core — all providers): ActivityNodeId columns in ActivityExecutionRecords and WorkflowExecutionLogRecords have been widened to unlimited types (nvarchar(max) / longtext / NCLOB) to support deeply nested workflows. The corresponding B-tree indexes (IX_ActivityExecutionRecord_ActivityNodeId, IX_WorkflowExecutionLogRecord_ActivityNodeId) are dropped as part of the V3_6 migrations. You must apply the EF Core migrations before upgrading to 3.6.0 in any SQL Server, MySQL, or Oracle deployment. (d4b69be44b) (#​7338)

  • Multitenancy — tenant ID convention change: An empty string ("") is now the canonical default tenant ID for all tenant-aware entities; null now means tenant-agnostic (visible to all tenants). EF Core query filters and the ActivityRegistry have been updated accordingly. If your database contains rows with a null TenantId that were intended to represent the default tenant, migrate those rows to "" before upgrading. The new NormalizeTenantId() extension method on string handles the conversion in code. (#​7217, #​7226)

  • Multitenancy — stored-trigger index updated: Database indexes on stored triggers now include TenantId. The V3_6 migration adds this index; no manual action is required beyond running migrations. (#​7217)

  • DefaultRegistriesPopulator constructor change: The constructor now requires an additional INotificationSender dependency. If you manually instantiate or override DefaultRegistriesPopulator in tests or custom DI registrations, add the new parameter. Standard DI consumers are unaffected. (#​7293)

  • Elsa.Common dependency trimmed: The DistributedLock meta-package (which pulled in all provider implementations) has been replaced with DistributedLock.Core. Applications that relied on the transitive provider packages (e.g. DistributedLock.SqlServer) being pulled in via Elsa.Common must add explicit package references. (53245cafbd) (#​7169)

✨ New features

Activity host registration

  • HostMethodActivity / activity hosts: Introduces support for registering CLR types as activity hosts. Public async methods on a registered type are automatically discovered and exposed as individual activities in the workflow designer, enabling code-first activity generation without manual activity boilerplate. New types: HostMethodActivity, HostMethodActivityProvider, IHostMethodActivityDescriber, FromServicesAttribute. (fa04e1ebcd) (#​7172)

Workflow dispatch notifications

  • Dispatch lifecycle notifications: BackgroundWorkflowDispatcher now emits four new notifications at dispatch time, allowing subscribers to react to durable dispatch scenarios without a custom dispatcher:

    • WorkflowDefinitionDispatching / WorkflowDefinitionDispatched
    • WorkflowInstanceDispatching / WorkflowInstanceDispatched

    (411ca0a332) (#​7157)

  • WorkflowDefinitionsReloaded notification: DefaultRegistriesPopulator now dispatches a WorkflowDefinitionsReloaded notification after repopulating the workflow definition store, enabling subscriber nodes to synchronize their registries. (f5505d66c9) (#​7293)

Consumers API & recursive export

  • GET /workflow-definitions/{definitionId}/consumers: New endpoint returns all recursive consuming workflow definitions for a given definition. Built on a new IWorkflowReferenceGraphBuilder / WorkflowReferenceGraph model that replaces the previous ad-hoc recursive query approach. (0a2e99ad42) (#​7309)

  • Export with transitive consumers: The export endpoint and BulkExportWorkflowDefinitionsRequest now accept an IncludeConsumingWorkflows flag (default false). When enabled, the ZIP export recursively resolves and includes all consuming workflows at their latest version. Exported filenames are now deterministic ({Name}-{DefinitionId}.json). (0a2e99ad42) (#​7309)

Default commit strategies

  • Global default commit strategies: New WithDefaultWorkflowCommitStrategy() and WithDefaultActivityCommitStrategy() extension methods on the workflows builder let you set application-wide fallback commit strategies. The resolution order for activities is: activity-specific → default activity → workflow-specific → default workflow → no commit. Default strategies are stored separately from the registry so they don't appear in the UI/tooling. (31eff52d24) (#​7148)

Multitenancy enhancements

  • Null TenantId for tenant-agnostic entities: Entities with a null TenantId are now treated as visible across all tenants. EF Core query filters and ActivityRegistry query methods include null-tenanted records in every tenant's scope. New ActivityDescriptor.TenantId (nullable) property added. (7bc9035f5e) (#​7226)

... (truncated)

3.6.0-rc5

What's Changed

Full Changelog: elsa-workflows/elsa-core@3.6.0-rc4...3.6.0-rc5

3.6.0-rc4

What's Changed

Full Changelog: elsa-workflows/elsa-core@3.6.0-rc3...3.6.0-rc4

3.6.0-rc3

Compare: 3.6.0-rc2...3.6.0-rc3

This release candidate includes significant multitenancy improvements, bug fixes, and enhanced test coverage.

⚠️ Breaking changes / upgrade notes

Multitenancy Tenant ID Convention Changes

Affected users: Applications using multitenancy features, especially those with existing tenant data.

What changed:

  • Default tenant ID convention: The default tenant now uses an empty string ("") instead of null (ADR-0008). (b09a56481) (#​7217)
  • Tenant-agnostic entity convention: Tenant-agnostic entities (visible to all tenants) now use asterisk ("*") as the sentinel value instead of null (ADR-0009). (7bc9035f5) (#​7226)
  • Database schema impact: Database indexes on the Triggers table now include TenantId in unique constraints across all EF Core providers. (b09a56481) (#​7217)

Migration required:

  • Convert existing null TenantId values to empty strings for default tenant data in WorkflowDefinitions, WorkflowInstances, and runtime entities.
  • Review ADR-0008 (Default Tenant ID) and ADR-0009 (Tenant-Agnostic Entities) in doc/adr/ for detailed rationale and migration guidance.

Query filter changes: EF Core query filters have been updated to handle the new tenant ID conventions, ensuring tenant isolation is properly maintained. (7bc9035f5) (#​7226)

✨ New features

Multitenancy enhancements

  • Configuration-based multitenancy: Introduced configuration-based tenant provider to streamline tenant initialization and customization. (b09a56481) (#​7217)
  • Tenant-agnostic workflow support: Workflows and activities can now be marked as tenant-agnostic (using "*" as tenant ID) to make them accessible across all tenants. (7bc9035f5) (#​7226)
  • Selective lock mocking in tests: Added SelectiveMockLockProvider for precise lock mocking in tests without affecting unrelated background operations. (b09a56481) (#​7217)

🔧 Improvements

Multitenancy

  • Tenant filtering in workflow store populator: Added tenant-specific filtering in DefaultWorkflowDefinitionStorePopulator to ensure workflows are only loaded for the current tenant. (b09a56481) (#​7217)
  • Tenant isolation in activity provider: Enforced tenant isolation in WorkflowDefinitionActivityProvider and included tenant ID in activity type names for better separation. (558902bb7)
  • Optimized activity registry: Improved ActivityRegistry.Find to prefer tenant-specific descriptors over tenant-agnostic ones with single-pass iteration for better performance. (7bc9035f5) (#​7226)
  • Tenant headers support: Added tenant headers support to BackgroundWorkflowCancellationDispatcher for proper tenant context propagation during workflow cancellation. (bc70beff1) (#​7040)

API improvements

  • Labels endpoints migration: Updated Labels endpoints to use ElsaEndpoint base class with standardized permission configuration. (72569702f) (#​7205)

Error handling

... (truncated)

3.6.0-rc2

Compare: 3.6.0-rc1...3.6.0-rc2

⚠️ Breaking changes / upgrade notes

  • CI / SDK: GitHub workflow now uses .NET SDK 10.x (was 9.x). (b22956c792) (fa2254f41b) (72597f733f)
  • Bookmarks model change: Bookmark moved from a positional record to a mutable class (serialization/back-compat oriented). (ca268c16ad) (#​7161)
  • DistributedLock package: Elsa.Common now references DistributedLock.Core instead of DistributedLock. (#​7169)

✨ New features

Activity hosts / host-method activities

  • Introduced host-method activities: expose public methods on configured CLR types as workflow activities. (#​7172)
    • Parameter binding extensibility (e.g. DI-backed parameters using [FromServices]). (#​7172)
  • Added a sample activity host (Penguin) and registered it in Elsa.Server.Web. (#​7172)

Commit strategies (defaults)

  • Added support for global default commit strategies (fallback when no explicit strategy is configured). (#​7148)

Resilience / transient exception detection

  • Added transient exception detection infrastructure and registration. (ca268c16ad) (#​7161)

Workflow dispatch notifications

  • Added new notifications emitted by the background dispatcher. (#​7157)

Tenant task lifecycle & dependencies

  • Introduced TenantTaskManager and dependency ordering support ([TaskDependency], TopologicalTaskSorter). (#​7174)

🔧 Improvements

  • Distributed runtime lock resilience: Polly retry around distributed lock acquisition (with transient exception detection), and safer lock release behavior. (#​7161)
  • Mediator background services: improved cancellation handling to avoid noisy failures. (ca268c16ad) (#​7161)
  • Xunit logging: suppress “no currently active test” errors from late background log writes. (ca268c16ad) (#​7161)
  • Small cleanups:
    • Make correlationId parameter non-optional in WorkflowExecutionContext constructor. (fa798b0a47)
    • Remove unused ClearCompletionCallbacks from WorkflowExecutionContext. (79a64e90fd)

🐛 Fixes

  • Literal inputs: ActivityExecutionContext.TryGet(...) correctly handles Literal references by returning the literal’s value directly. (#​7075)

🧩 Developer-facing changes

  • Attribute usage expanded:
    • ActivityAttribute: now valid on classes, interfaces, and methods. (3778a14e54)
    • InputAttribute: now valid on properties and parameters. (3778a14e54)
    • OutputAttribute: now valid on properties, classes, methods, and return values. (3778a14e54)

🧪 Tests

  • Added/expanded coverage for:
    • Host method activity registration & descriptor behavior. (#​7172)
    • Distributed lock resilience (acquisition retries + release failure behavior). (#​7161)
    • Literal input handling. (#​7075)
    • Default workflow/activity commit strategy behavior. (#​7148)
    • Workflow dispatch notifications. (#​7157)
    • Tenant task dependency ordering / topological sorting. (#​7174)
      ... (truncated)

3.6.0-rc1

Elsa Workflows 3.6.0 RC1

This release focuses on Flowchart execution improvements, stronger runtime correctness, major test coverage expansion, reliability fixes for scheduling/triggers and HTTP content handling, and a platform upgrade to .NET 10 while retaining support for .NET 8 and .NET 9.

Highlights

  • Token-centric Flowchart execution model with configurable MergeMode, plus multiple refinements and DI-based configuration (opt-in). See Flowchart: token-based execution + per-activity MergeMode. (PRs: #​6632, #​6937, #​6993, #​7141)
  • Upgrade to .NET 10 across the solution (with conditional compatibility dependencies where needed). (PR: #​7062)
  • New Activity Testing API and a major expansion of unit/integration/component test coverage across core activities, scheduling, HTTP endpoints, JavaScript, and flowchart execution. (PR: #​6719 and many follow-ups)
  • Improved runtime observability & execution record serialization, including snapshots and a new ActivityCompleted notification. (PRs: #​6675, #​6800, #​6807)
  • Reliability fixes across triggers/scheduling and HTTP content handling (cron delay edge cases, multi-engine trigger registration, Content-Length / charset issues). (PRs: #​7047, #​7131, #​6676, #​7027)

Flowchart: token-based execution + per-activity MergeMode (opt-in)

Elsa 3.6.0 introduces an optional token-based execution algorithm for the Flowchart activity. Instead of relying on the previous counter-based scheduling model, the Flowchart can now track progress using tokens that represent a taken connection (from a source activity outcome to a target activity).

When an activity completes, the flowchart:

  • Emits tokens for each taken outbound connection (based on the activity’s outcome names).
  • Consumes inbound tokens that were waiting for the completed activity.
  • Schedules downstream activities based on each target activity’s MergeMode.

New: MergeMode (configurable per activity)

With token-based execution enabled, Flowchart supports a new MergeMode concept that determines how a node behaves when it has multiple inbound connections. You can now specify a merge mode per activity, allowing different “join” semantics within the same flowchart.

In broad terms, merge modes enable behaviors like:

  • Stream-like behavior: proceeds without strict joining, helping avoid dead-path waiting.
  • Forward-join behavior (Merge): waits for tokens from all forward inbound connections (loop/back edges don’t block).
  • Strict join behavior (Converge): waits for tokens from all inbound connections, including loop/back edges.
  • First-arrival behavior (Cascade / Race): schedules on the first arriving inbound token; in Race mode, other inbound ancestors are canceled so only the “winning” path continues.

This improves predictability for joins, forks, and cyclic graphs, while giving you fine-grained control over how each activity merges incoming paths.

How to opt in (Program.cs)

Token-based Flowchart execution is opt-in. Enable it via the Flowchart feature configuration:

elsa.UseFlowchart(flowchart => flowchart.UseTokenBasedExecution())

Breaking / Upgrading Notes

These are the changes most likely to affect upgrades from 3.5.x.

1) Multi-targeting: .NET 8, .NET 9, and .NET 10

Elsa 3.6.0 multi-targets .NET 8, .NET 9, and .NET 10.

  • Most consumers can continue targeting .NET 8 or .NET 9.
    ... (truncated)

Commits viewable in compare view.

Updated Elsa.Workflows.Api from 3.5.3 to 3.6.0.

Release notes

Sourced from Elsa.Workflows.Api's releases.

3.6.0

Elsa 3.6.0 — Release Notes

Compare: 3.5.3...3.6.0

⚠️ Breaking changes / upgrade notes

  • Database migrations (EF Core — all providers): ActivityNodeId columns in ActivityExecutionRecords and WorkflowExecutionLogRecords have been widened to unlimited types (nvarchar(max) / longtext / NCLOB) to support deeply nested workflows. The corresponding B-tree indexes (IX_ActivityExecutionRecord_ActivityNodeId, IX_WorkflowExecutionLogRecord_ActivityNodeId) are dropped as part of the V3_6 migrations. You must apply the EF Core migrations before upgrading to 3.6.0 in any SQL Server, MySQL, or Oracle deployment. (d4b69be44b) (#​7338)

  • Multitenancy — tenant ID convention change: An empty string ("") is now the canonical default tenant ID for all tenant-aware entities; null now means tenant-agnostic (visible to all tenants). EF Core query filters and the ActivityRegistry have been updated accordingly. If your database contains rows with a null TenantId that were intended to represent the default tenant, migrate those rows to "" before upgrading. The new NormalizeTenantId() extension method on string handles the conversion in code. (#​7217, #​7226)

  • Multitenancy — stored-trigger index updated: Database indexes on stored triggers now include TenantId. The V3_6 migration adds this index; no manual action is required beyond running migrations. (#​7217)

  • DefaultRegistriesPopulator constructor change: The constructor now requires an additional INotificationSender dependency. If you manually instantiate or override DefaultRegistriesPopulator in tests or custom DI registrations, add the new parameter. Standard DI consumers are unaffected. (#​7293)

  • Elsa.Common dependency trimmed: The DistributedLock meta-package (which pulled in all provider implementations) has been replaced with DistributedLock.Core. Applications that relied on the transitive provider packages (e.g. DistributedLock.SqlServer) being pulled in via Elsa.Common must add explicit package references. (53245cafbd) (#​7169)

✨ New features

Activity host registration

  • HostMethodActivity / activity hosts: Introduces support for registering CLR types as activity hosts. Public async methods on a registered type are automatically discovered and exposed as individual activities in the workflow designer, enabling code-first activity generation without manual activity boilerplate. New types: HostMethodActivity, HostMethodActivityProvider, IHostMethodActivityDescriber, FromServicesAttribute. (fa04e1ebcd) (#​7172)

Workflow dispatch notifications

  • Dispatch lifecycle notifications: BackgroundWorkflowDispatcher now emits four new notifications at dispatch time, allowing subscribers to react to durable dispatch scenarios without a custom dispatcher:

    • WorkflowDefinitionDispatching / WorkflowDefinitionDispatched
    • WorkflowInstanceDispatching / WorkflowInstanceDispatched

    (411ca0a332) (#​7157)

  • WorkflowDefinitionsReloaded notification: DefaultRegistriesPopulator now dispatches a WorkflowDefinitionsReloaded notification after repopulating the workflow definition store, enabling subscriber nodes to synchronize their registries. (f5505d66c9) (#​7293)

Consumers API & recursive export

  • GET /workflow-definitions/{definitionId}/consumers: New endpoint returns all recursive consuming workflow definitions for a given definition. Built on a new IWorkflowReferenceGraphBuilder / WorkflowReferenceGraph model that replaces the previous ad-hoc recursive query approach. (0a2e99ad42) (#​7309)

  • Export with transitive consumers: The export endpoint and BulkExportWorkflowDefinitionsRequest now accept an IncludeConsumingWorkflows flag (default false). When enabled, the ZIP export recursively resolves and includes all consuming workflows at their latest version. Exported filenames are now deterministic ({Name}-{DefinitionId}.json). (0a2e99ad42) (#​7309)

Default commit strategies

  • Global default commit strategies: New WithDefaultWorkflowCommitStrategy() and WithDefaultActivityCommitStrategy() extension methods on the workflows builder let you set application-wide fallback commit strategies. The resolution order for activities is: activity-specific → default activity → workflow-specific → default workflow → no commit. Default strategies are stored separately from the registry so they don't appear in the UI/tooling. (31eff52d24) (#​7148)

Multitenancy enhancements

  • Null TenantId for tenant-agnostic entities: Entities with a null TenantId are now treated as visible across all tenants. EF Core query filters and ActivityRegistry query methods include null-tenanted records in every tenant's scope. New ActivityDescriptor.TenantId (nullable) property added. (7bc9035f5e) (#​7226)

... (truncated)

3.6.0-rc5

What's Changed

Full Changelog: elsa-workflows/elsa-core@3.6.0-rc4...3.6.0-rc5

3.6.0-rc4

What's Changed

Full Changelog: elsa-workflows/elsa-core@3.6.0-rc3...3.6.0-rc4

3.6.0-rc3

Compare: 3.6.0-rc2...3.6.0-rc3

This release candidate includes significant multitenancy improvements, bug fixes, and enhanced test coverage.

⚠️ Breaking changes / upgrade notes

Multitenancy Tenant ID Convention Changes

Affected users: Applications using multitenancy features, especially those with existing tenant data.

What changed:

  • Default tenant ID convention: The default tenant now uses an empty string ("") instead of null (ADR-0008). (b09a56481) (#​7217)
  • Tenant-agnostic entity convention: Tenant-agnostic entities (visible to all tenants) now use asterisk ("*") as the sentinel value instead of null (ADR-0009). (7bc9035f5) (#​7226)
  • Database schema impact: Database indexes on the Triggers table now include TenantId in unique constraints across all EF Core providers. (b09a56481) (#​7217)

Migration required:

  • Convert existing null TenantId values to empty strings for default tenant data in WorkflowDefinitions, WorkflowInstances, and runtime entities.
  • Review ADR-0008 (Default Tenant ID) and ADR-0009 (Tenant-Agnostic Entities) in doc/adr/ for detailed rationale and migration guidance.

Query filter changes: EF Core query filters have been updated to handle the new tenant ID conventions, ensuring tenant isolation is properly maintained. (7bc9035f5) (#​7226)

✨ New features

Multitenancy enhancements

  • Configuration-based multitenancy: Introduced configuration-based tenant provider to streamline tenant initialization and customization. (b09a56481) (#​7217)
  • Tenant-agnostic workflow support: Workflows and activities can now be marked as tenant-agnostic (using "*" as tenant ID) to make them accessible across all tenants. (7bc9035f5) (#​7226)
  • Selective lock mocking in tests: Added SelectiveMockLockProvider for precise lock mocking in tests without affecting unrelated background operations. (b09a56481) (#​7217)

🔧 Improvements

Multitenancy

  • Tenant filtering in workflow store populator: Added tenant-specific filtering in DefaultWorkflowDefinitionStorePopulator to ensure workflows are only loaded for the current tenant. (b09a56481) (#​7217)
  • Tenant isolation in activity provider: Enforced tenant isolation in WorkflowDefinitionActivityProvider and included tenant ID in activity type names for better separation. (558902bb7)
  • Optimized activity registry: Improved ActivityRegistry.Find to prefer tenant-specific descriptors over tenant-agnostic ones with single-pass iteration for better performance. (7bc9035f5) (#​7226)
  • Tenant headers support: Added tenant headers support to BackgroundWorkflowCancellationDispatcher for proper tenant context propagation during workflow cancellation. (bc70beff1) (#​7040)

API improvements

  • Labels endpoints migration: Updated Labels endpoints to use ElsaEndpoint base class with standardized permission configuration. (72569702f) (#​7205)

Error handling

... (truncated)

3.6.0-rc2

Compare: 3.6.0-rc1...3.6.0-rc2

⚠️ Breaking changes / upgrade notes

  • CI / SDK: GitHub workflow now uses .NET SDK 10.x (was 9.x). (b22956c792) (fa2254f41b) (72597f733f)
  • Bookmarks model change: Bookmark moved from a positional record to a mutable class (serialization/back-compat oriented). (ca268c16ad) (#​7161)
  • DistributedLock package: Elsa.Common now references DistributedLock.Core instead of `Distribut...

_Descriptio...

Description has been truncated

@dependabot
Bump the elsa group with 4 updates
38755e0 
Bumps Elsa from 3.5.3 to 3.6.0
Bumps Elsa.Identity from 3.5.3 to 3.6.0
Bumps Elsa.Scheduling from 3.5.3 to 3.6.0
Bumps Elsa.Workflows.Api from 3.5.3 to 3.6.0

---
updated-dependencies:
- dependency-name: Elsa
  dependency-version: 3.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: elsa
- dependency-name: Elsa.Identity
  dependency-version: 3.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: elsa
- dependency-name: Elsa.Scheduling
  dependency-version: 3.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: elsa
- dependency-name: Elsa.Workflows.Api
  dependency-version: 3.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: elsa
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added .NET Pull requests that update .net code dependencies Pull requests that update a dependency file labels Mar 5, 2026
@github-actions github-actions bot merged commit 3c462e2 into master Mar 5, 2026
1 of 2 checks passed
@github-actions github-actions bot deleted the dependabot/nuget/Elsademo/ElsaCore.Server/elsa-61cc1c1380 branch March 5, 2026 17:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@github-actions github-actions[bot] github-actions[bot] approved these changes

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .net code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants