Bump Elsa.Workflows.Api from 3.5.3 to 3.7.0 - #7
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
--- updated-dependencies: - dependency-name: Elsa.Workflows.Api dependency-version: 3.7.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/nuget/src/BioTrace.Elsa.Abp.AspNetCore/develop/Elsa.Workflows.Api-3.7.0
branch
June 11, 2026 07:45
8 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated Elsa.Workflows.Api from 3.5.3 to 3.7.0.
Release notes
Sourced from Elsa.Workflows.Api's releases.
3.7.0
What's Changed
New Contributors
Full Changelog: elsa-workflows/elsa-core@3.6.0...3.7.0
3.7.0-rc1
Compare:
3.7.0-preview1...3.7.0-rc1✨ New features
Modular server runtime
Elsa.Workflows.Runtime.Distributedand configured all shells with the core workflow, runtime, management, distributed runtime, and API shell features. (e7eaa4b1fe)🔧 Improvements
HttpJavaScriptFeaturedependency onJavaScriptFeatureso shell feature activation includes the required JavaScript integration first. (ad90e81af9)WorkflowManagementFeature, making exporter services available through shell feature setup. (ad90e81af9)🐛 Fixes
GetFriendlyTypeNamefor arrays of generic and nested generic types, including multi-dimensional arrays, by resolving array element types before generic formatting. (b88af1e023) (#7400)🧩 Developer-facing changes
WorkflowManagementFeaturenow receiveIWorkflowDefinitionExporterandIFileNameSanitizerregistrations by default. (ad90e81af9)Elsa.HttpandElsa.Workflows.Runtime.Distributed, reflecting the expected feature set for distributed runtime and HTTP activity configuration. (e7eaa4b1fe) (ad90e81af9)🧪 Tests
TypeExtensions.GetFriendlyTypeName, including non-generic types, generic types, arrays of generic types, nested generic arrays, multi-dimensional arrays, and square bracket formatting. (b88af1e023) (#7400)🔁 CI / Build
📦 Full changelog (short)
Elsa.Workflows.Runtime.DistributedintoElsa.ModularServer.Weband configure shell features for enhanced distributed runtime support. (e7eaa4b1fe)HttpFeaturedependencies, and add new identity persistence options. (ad90e81af9)... (truncated)
3.7.0-preview1
Full Changelog: elsa-workflows/elsa-core@3.7.0-preview1...3.7.0-preview1
What's Changed
New Contributors
Full Changelog: elsa-workflows/elsa-core@3.6.1...3.7.0-preview1
3.6.2
Elsa 3.6.2 is a patch release that addresses a NuGet security warning caused by a vulnerable transitive dependency.
Security
Fixed
NU1903warnings/errors forSnappier1.2.0, which has a known high-severity vulnerability: GHSA-pggp-6c3x-2xmx.Elsa did not reference
Snappierdirectly; it was introduced transitively through:Elsa now explicitly pins
Snappierto1.3.1, the first patched version.Notes
IronCompress, but it is used by Elsa’s Zstd compression codec.IronCompresswould require changing compression behavior and validating compatibility with already persisted compressed workflow data.Validation
dotnet list Elsa.sln package --include-transitiveresolvesSnappierto1.3.1.NU1903is no longer reported forSnappier.Elsa.Commonbuilds successfully.Full Changelog: elsa-workflows/elsa-core@3.6.1...3.6.2
3.6.1
What's Changed
New Contributors
Full Changelog: elsa-workflows/elsa-core@3.6.0...3.6.1
3.6.0
Elsa 3.6.0 — Release Notes
Compare:
3.5.3...3.6.0EF Core package names have changed: EF Core persistence packages were renamed from
Elsa.EntityFrameworkCore.*toElsa.Persistence.EFCore.*. If your application references any of the old package names, you must update them to the new package names when upgrading to 3.6.0. Be sure to review your project files, internal package feeds, CI pipelines, and deployment manifests for old package references.Kafka and file storage packages moved to Elsa Extensions:
Elsa.KafkaandElsa.FileStorageno longer ship fromelsa-coreas of 3.6.0. They were moved to theelsa-extensionsrepository and renamed as part of the extension package namespace realignment:Elsa.Kafka->Elsa.ServiceBus.KafkaElsa.FileStorage->Elsa.Storage.FilesWhen upgrading from 3.5.x, replace the old package references with the new
elsa-extensionspackages and update namespaces/usings accordingly.Elsa.ServiceBus.Kafkais the Kafka replacement package.Scripting package names have changed:
Database migrations (EF Core — all providers):
ActivityNodeIdcolumns inActivityExecutionRecordsandWorkflowExecutionLogRecordshave 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;nullnow means tenant-agnostic (visible to all tenants). EF Core query filters and theActivityRegistryhave been updated accordingly. If your database contains rows with anullTenantIdthat were intended to represent the default tenant, migrate those rows to""before upgrading. The newNormalizeTenantId()extension method onstringhandles 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)DefaultRegistriesPopulatorconstructor change: The constructor now requires an additionalINotificationSenderdependency. If you manually instantiate or overrideDefaultRegistriesPopulatorin tests or custom DI registrations, add the new parameter. Standard DI consumers are unaffected. (#7293)Elsa.Commondependency trimmed: TheDistributedLockmeta-package (which pulled in all provider implementations) has been replaced withDistributedLock.Core. Applications that relied on the transitive provider packages (e.g.DistributedLock.SqlServer) being pulled in viaElsa.Commonmust add explicit package references. (53245cafbd) (#7169)✨ New features
Activity host registration
HostMethodActivity/ activity hosts: Introduces support for registering CLR types as activity hosts. Publicasyncmethods 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:
BackgroundWorkflowDispatchernow emits four new notifications at dispatch time, allowing subscribers to react to durable dispatch scenarios without a custom dispatcher:WorkflowDefinitionDispatching/WorkflowDefinitionDispatchedWorkflowInstanceDispatching/WorkflowInstanceDispatched(411ca0a332) (#7157)
WorkflowDefinitionsReloadednotification:DefaultRegistriesPopulatornow dispatches aWorkflowDefinitionsReloadednotification after repopulating the workflow definition store, enabling subscriber nodes to synchronize their registries. (f5505d66c9) (#7293)... (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
Resulthandling: by @sfmskywalker in Update multitenancy logic and improveResulthandling: elsa-workflows/elsa-core#7281Full 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-rc3This release candidate includes significant multitenancy improvements, bug fixes, and enhanced test coverage.
Multitenancy Tenant ID Convention Changes
Affected users: Applications using multitenancy features, especially those with existing tenant data.
What changed:
"") instead ofnull(ADR-0008). (b09a56481) (#7217)"*") as the sentinel value instead ofnull(ADR-0009). (7bc9035f5) (#7226)Triggerstable now includeTenantIdin unique constraints across all EF Core providers. (b09a56481) (#7217)Migration required:
nullTenantIdvalues to empty strings for default tenant data inWorkflowDefinitions,WorkflowInstances, and runtime entities.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
"*"as tenant ID) to make them accessible across all tenants. (7bc9035f5) (#7226)SelectiveMockLockProviderfor precise lock mocking in tests without affecting unrelated background operations. (b09a56481) (#7217)🔧 Improvements
Multitenancy
DefaultWorkflowDefinitionStorePopulatorto ensure workflows are only loaded for the current tenant. (b09a56481) (#7217)WorkflowDefinitionActivityProviderand included tenant ID in activity type names for better separation. (558902bb7)ActivityRegistry.Findto prefer tenant-specific descriptors over tenant-agnostic ones with single-pass iteration for better performance. (7bc9035f5) (#7226)BackgroundWorkflowCancellationDispatcherfor proper tenant context propagation during workflow cancellation. (bc70beff1) (#7040)API improvements
ElsaEndpointbase class with standardized permission configuration. (72569702f) (#7205)Error handling
... (truncated)
3.6.0-rc2
Compare:
3.6.0-rc1...3.6.0-rc2Bookmarkmoved from a positional record to a mutable class (serialization/back-compat oriented). (ca268c16ad) (#7161)Elsa.Commonnow referencesDistributedLock.Coreinstead ofDistributedLock. (#7169)✨ New features
Activity hosts / host-method activities
[FromServices]). (#7172)Penguin) and registered it inElsa.Server.Web. (#7172)Commit strategies (defaults)
Resilience / transient exception detection
Workflow dispatch notifications
Tenant task lifecycle & dependencies
TenantTaskManagerand dependency ordering support ([TaskDependency],TopologicalTaskSorter). (#7174)🔧 Improvements
correlationIdparameter non-optional inWorkflowExecutionContextconstructor. (fa798b0a47)ClearCompletionCallbacksfromWorkflowExecutionContext. (79a64e90fd)🐛 Fixes
ActivityExecutionContext.TryGet(...)correctly handlesLiteralreferences by returning the literal’s value directly. (#7075)🧩 Developer-facing changes
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
... (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
MergeMode. (PRs: #6632, #6937, #6993, #7141)ActivityCompletednotification. (PRs: #6675, #6800, #6807)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:
MergeMode.New:
MergeMode(configurable per activity)With token-based execution enabled, Flowchart supports a new
MergeModeconcept 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:
Merge): waits for tokens from all forward inbound connections (loop/back edges don’t block).Converge): waits for tokens from all inbound connections, including loop/back edges.Cascade/Race): schedules on the first arriving inbound token; inRacemode, 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:
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.
... (truncated)
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)