> For the complete documentation index, see [llms.txt](https://docs.elsaworkflows.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elsaworkflows.io/getting-started/packages.md).

# Packages

Elsa is available as a collection of NuGet packages. Some packages are required for executing workflows, while others provide integrations with systems like service buses, cloud services, and additional features such as [email delivery](/activities/email.md), [CSV processing](/activities/csv.md), [GitHub automation](/activities/github.md), or [OpenTelemetry workflow/activity tracing](/extensibility/opentelemetry-tracing.md), or [Telnyx voice and webhook automation](/activities/telnyx.md).

{% hint style="info" %}
The current stable package line is Elsa **3.8.0**, published on NuGet.org. Pin the Elsa packages used by an application to the same `3.8.0` version while upgrading; do not mix stable, RC, and preview builds.
{% endhint %}

## **Main Package**

The primary package you'll need to get started with Elsa is the `Elsa` package. It's a bundle that includes the following essential packages:

* Elsa.Api.Common
* Elsa.Mediator
* Elsa.Workflows.Core
* Elsa.Workflows.Management
* Elsa.Workflows.Runtime

To install the core `Elsa` package, use the `dotnet` CLI:

```
dotnet add package Elsa --version 3.8.0
```

## **Project Templates**

For a new .NET 10 server, Studio, or combined application, install the exact stable template package:

```bash
dotnet new install Elsa.Templates@3.8.0
```

See [Upgrade to Elsa 3.8.0](/getting-started/upgrading-to-3.8.md#start-from-the-elsa-templates) for the supported generation options, feature models, authentication choices, and local Development identity defaults. The [Elsa.Templates 3.8.0 GitHub release](https://github.com/elsa-workflows/elsa-templates/releases/tag/3.8.0) contains the package release details.

## **Package Feeds**

Elsa packages are distributed through various feeds based on their stability and release phase:

<table><thead><tr><th width="228">Type</th><th width="100">Feed</th><th>URL</th></tr></thead><tbody><tr><td>Releases</td><td>NuGet</td><td>https://api.nuget.org/v3/index.json</td></tr><tr><td>Release Candidates</td><td>NuGet</td><td>https://api.nuget.org/v3/index.json</td></tr><tr><td>Previews</td><td>Feedz (when published)</td><td>https://f.feedz.io/elsa-workflows/elsa-3/nuget/index.json</td></tr></tbody></table>

### **Releases** <a href="#releases" id="releases"></a>

Stable versions of Elsa are distributed via NuGet.org.

### **Release Candidates (RC)** <a href="#release-candidates-rc" id="release-candidates-rc"></a>

RC packages are also available on NuGet.org. They offer a sneak peek into upcoming features, allowing users to test and provide feedback before the final release. While RC packages are generally stable, they might still undergo changes before the final release.

### **Previews** <a href="#previews" id="previews"></a>

Preview versions are a separate prerelease channel and may introduce breaking changes. Feedz availability and publication timing are independent of the Elsa 3.8.0 stable release; use the feed only when the relevant release notes or branch instructions confirm that a preview package is available. Stable 3.8.0 applications should use NuGet.org and should not add the preview source.

To access preview packages, include the feed URL when using the dotnet CLI or add it to your `NuGet.config`:

```xml
<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <clear />
    <add key="NuGet official package source" value="https://api.nuget.org/v3/index.json" />
    <add key="Elsa 3 preview" value="https://f.feedz.io/elsa-workflows/elsa-3/nuget/index.json" />
  </packageSources>
</configuration>
```

{% hint style="warning" %}
**Preview Packages**

Ensure the "Preview" checkbox is ticked in your NuGet explorer to view the preview packages.
{% endhint %}

## **Versioning Strategy** <a href="#versioning-strategy" id="versioning-strategy"></a>

Elsa uses to the following versioning strategy:

* **Released** packages: Major.Minor.Revision (e.g., `3.8.0`)
* **Release Candidate** packages: Major.Minor.Revision-rcX (e.g., `3.8.0-rc1`)
* **Preview** packages: Major.Minor.Revision-preview\.X (e.g., `3.8.0-preview.1`)

The major version remains consistent unless significant changes occur. New features increment the minor version, while fixes or minor improvements bump the revision number.\\