3.9.0

Elsa.Templates 3.9.0

This release aligns the dotnet new templates with the stable Elsa 3.9.0 Core and Studio packages.

Install or update

dotnet new install Elsa.Templates@3.9.0

The package provides elsa-server, elsa-studio and elsa-combined. Generated projects require the .NET 10 SDK.

Changes

• Generated Elsa and Elsa Studio package references now use 3.9.0. CShells stays at 0.0.28. Template package 3.8.0 generated Elsa 3.8.0 references.
• Studio branding identifies the 3.9 release.
• Release packaging fails fast on an empty feedz.io or nuget.org API key, and the NuGet publication recovery path is repaired.

Upgrading generated applications

Updating the template package changes future scaffolding; it doesn't update existing applications. To upgrade an existing application, align its Elsa package references to 3.9.0 and follow the Upgrading to Elsa 3.9 guide. 3.9.0 renames permissions, shortens the default access token lifetime and removes the localhost SecurityRoot grant. See the Core release notes and Studio release notes.

Known limitations

• On first start, a freshly generated server logs an Elsa.Identity error saying no users exist, even though the template defines users in configuration. Sign-in and API calls work normally.

Implementation: Release packaging guard (#10) and Bump to Elsa 3.9.0 (#11).

Full changelog: 3.8.0...3.9.0

3.8.0

Elsa.Templates 3.8.0

This release aligns the dotnet new templates with the stable Elsa 3.8.0 Core and Studio packages.

Install or update

dotnet new install Elsa.Templates@3.8.0

The package provides elsa-server, elsa-studio, and elsa-combined, including the existing static/shell feature models and Server, WebAssembly, and hybrid Studio hosting options. Generated projects require the .NET 10 SDK.

Changes

• Generated Elsa package references now use 3.8.0 and CShells references use 0.0.28. The previous template package 3.7.1 generated Elsa 3.7.0 references.
• Studio branding identifies the 3.8 release.
• Server and combined hosts enable the Dashboard API and workflow dashboard data provider used by the Studio landing page.
• .NET 10 host projects explicitly include the Blazor framework assets required when UI components come from packages.
• Hybrid hosts give their Server and WebAssembly pages distinct routes, so the configured hosting mode selects the correct page without ambiguous root routing.
• Generated Studio hosts register the shared authentication UI and the selected authentication mode required by 3.8.0, and pass the selected backend authentication configuration to the dashboard API client.
• Release packaging records and verifies the source commit, and subscribes once to GitHub release publication for both stable and prerelease releases.
• Generated-project checks verify configuration, authentication composition, and embedded dependency versions across 20 representative template combinations.
• Public sample identity credentials are confined to Development configuration. Shell hosts register identity and administrator bootstrap features, and static hosts bind API route settings through Api:RoutePrefix.

Upgrading generated applications

Updating the template package changes future scaffolding; it does not update existing applications. Align an existing application's Elsa package references to 3.8.0 and review the Core release notes and Studio release notes, especially identity configuration and host-code execution defaults.

Implementation: Release Elsa templates 3.8.0 (#4) and Dashboard authentication (#5).

Full changelog: 3.7.1...3.8.0

3.7.1

What's Changed

• [codex] Map health checks to dedicated endpoint by @sfmskywalker in #2

Full Changelog: 3.7.0...3.7.1

3.7.0

What's Changed

• Migrate elsa-studio template to .NET 10 Blazor Web App model by @sfmskywalker in #1

New Contributors

• @sfmskywalker made their first contribution in #1

Full Changelog: https://github.com/elsa-workflows/elsa-templates/commits/3.7.0