Standalone Releases control the deployment of a single project or package. They are used to eliminate the overhead of creating and maintaining a Release with multiple pieces of content.
...
provided to simplify release management when using just one content item, which may be applicable for emergency releases or it may be fit in normal operating mode for some projects.
...
Standalone Releases are linked directly to a project. Due to this, Standalone Releases can not be viewed within the standard Release Folder Structure. Instead, to view existing Standalone Releases for a project, navigate to the Releases tab on a project’s page.
...
Standalone Releases can be manually made for a project from the project’s Releases tab. Select the 
button in the top right of the table to open the create popup. The project and selected package will automatically be added to the Standalone Release’s content.
...
Recommended way to create Standalone release is directly from Build request dialog, please see details later in this document.
...
Field | Required | Description |
|---|---|---|
Release Name | Yes | The name of the standalone release. |
Pipeline | Yes | The pipeline which is used to process snapshots for the standalone release. (Uses default pipeline from the release settings setup of the Folder containing this Project) |
Description | No | An optional description for the standalone release. |
Package | Yes - If Package-Based Project | Name of package to be added to the standalone release. |
Build Environment | No | If there is only one build environment for project, then this will be defaulted. If no build environment specified and standalone release is setup for Scheduled Build, this project will not be included in Scheduled Build. |
Branch | Yes | The branch used for the project/package. |
Standalone Releases can also be automatically created when submitting a Build Request for a project. This can be done by selecting Create new Standalone Release from the release dropdown in a Build Request popup.
...