github elsa-workflows/elsa-core 3.10.2

one hour ago

Compare 3.10.1 to 3.10.2.


Highlights

Elsa 3.10.2 is a security update for the 3.10 line. It hardens workflow starts and bookmark resumes, tenant and role boundaries, workflow authoring, and recovery. Upgrade the Elsa packages together and review the steps below for the providers and features you use.


Upgrade notes

  • MassTransit and Proto.Actor. Drain pending starts with the old deployment before upgrading. Upgrade actor nodes and any custom grain implementations before enabling the upgraded consumers. Creation of an occupied workflow instance ID returns a conflict. Use the resume or run operation for an existing instance. Pending start upgrade steps
  • SQL Server EF Core. Check existing workflow definition and tenant ID key lengths before applying the Management index migration. Index preflight
  • Dapper. Apply management migration 10006 before serving workflow imports and runtime migration 20009 before starting the upgraded bookmark workers. The management migration reports conflicting retained version identities before creating its index. Review and resolve those rows before retrying. Valid queued work remains in place. Persistence upgrade · Bookmark queue upgrade
  • MongoDB and Elasticsearch. Multi-version publication and deletion, as well as saving a non-latest draft, require a transaction-capable MongoDB deployment. If you use custom Elasticsearch mappings, verify the documented exact-value fields for workflow instance and log queries. Workflow API · Elasticsearch mappings
  • Hosting and integrations. Configure per-source signing keys before enabling webhook traffic. Set the production Modular Server secrets key and use the documented rotation procedure if you are upgrading from the sample key. Configure credentials for the OTLP collector. Webhook delivery · Secrets key rotation · OTLP ingestion
  • Existing workflows. Review HTTP Endpoints with a policy configured and turn on Authorize where the policy should apply. Bulk dispatch accepts up to 100 instances per request. Review configured remote downloads, HTTP response buffering, and archive import limits. Workflow API · Capacity limits
  • VNext guest invitations. Index outstanding invitations or reissue them before reopening guest invitation verification. Upgrade steps

Security and reliability fixes

  • Preserve bookmark instance scope, reject duplicate instance creation, and apply the configured activation strategy to HTTP starts. Existing Elsa bookmark links retain their expiry.
  • Verify current role and tenant authority for sign-in, broker refresh, API keys, identity administration, and tenant administration.
  • Protect the exact authorized workflow versions when importing, editing, publishing, retracting, deleting, or updating BPMN. Grant instance restore only to trusted recovery operators.
  • Scope execution storage and caches to their authorized owners. Require explicit host authority for shared EF Core writes, and keep unreadable bookmark options in a durable dead-letter store where supported.
  • Limit the size of queued and buffered work, keep authorization data out of persisted HTTP activity output, and enforce access grants for AI tools and Platform integration.
  • Apply the patched .NET 10 WebAssembly debugger packages used by the released Blazor applications. Microsoft advisory

See the full changelog.

Don't miss a new elsa-core release

NewReleases is sending notifications on new releases.