# Releases

A Release is a combination of an MSquared Editor and an Engine Plugin. A Release allows customers to distribute their own content to their own user base along with the editor all in one go. Using Releases, customers can create and iterate on their own development kits to allow users to easily create content and experiences with a familar theme and feel.

{% hint style="info" %} <mark style="color:blue;">Right now, only one Engine Plugin can be bundles with an Editor to form a Release.</mark>
{% endhint %}

{% hint style="warning" %} <mark style="color:orange;">Each organisation currently only has one set of Releases and each new Release is considered an iterated version of the previous Release.</mark>

<mark style="color:orange;">This means users are able to upgrade from one release to another even if they are unrelated and when a new Release is created, it must have a greater semantic version than the previous one.</mark>
{% endhint %}

A Release has the following information:

<table><thead><tr><th width="212">Field Name (*Required)</th><th>Description</th></tr></thead><tbody><tr><td>Semantic Version</td><td>This must be a valid and increasing <a href="https://semver.org/">Semantic version</a>.</td></tr><tr><td>Version Title</td><td>A human-readable title to give to your Release.</td></tr><tr><td>Editor Version</td><td>The editor version to be used with your Release.</td></tr><tr><td>Assets</td><td>The Assets Version (Engine Plugin) to bundle with the selected Editor Version for this release.</td></tr><tr><td>Release Channels</td><td>The channel within the Launcher for this Release editor to appear in.<br><br><strong>This can be edited after the Release has been published</strong></td></tr><tr><td>Release Notes</td><td>A description of the changes in this Release.<br><br><strong>This can be edited after the Release has been published</strong></td></tr><tr><td>Breaking Changes</td><td>A description of the changes that may cause breakages in user projects upgrading to this Release.<br><br><strong>This can be edited after the Release has been published</strong></td></tr></tbody></table>

## Limitations

* The Assets Version (Engine Plugin) must be created with the same editor that you wish to bundle it with.

## Guides

<details>

<summary>Create a new Release</summary>

1. Downlaod the Editor that you wish to use as the `Editor Version`
2. Follow the guide to [Create an Engine Plugin](/platform-documentation/apis-and-tooling/dashboard/assets/engine-plugins.md#create-a-new-engine-plugin-assets) using this editor.
3. Navigate to the Releases page in the dashboard.
4. Click `New`.
5. Enter publish information for the new Release into the modal that opens.\
   \
   ![](/files/EkABlVFnEgFA1pwjopWK)\\
6. Click `Publish`.
7. You can now download or upgrade to this Release from the Launcher (you may need to restart the launcher).

</details>

<details>

<summary>Consume a new Release</summary>

Users are able to consume new Releases via the [Launcher](/platform-documentation/apis-and-tooling/launcher/msquared-launcher/editor-installations.md)

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.otherside.xyz/platform-documentation/apis-and-tooling/dashboard/releases.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.