How to Create a New Release

Updated 2 months ago by Copado Solutions

To create a new release, please follow the steps below:

  1. Click on the Releases tab.
  2. Click on New at the top right corner.
  3. Fill in the relevant fields:
    1. Give your release a name.
    2. Select the project to which your release is linked.
    3. Add a version. If you add a version to a release, when the promotion linked to this release is merged into the branch of the destination org, Copado tags the main branch with this version number.
      Please note that version names cannot contain blank spaces. Otherwise, the merge process will fail.
    4. Select a status.
    5. Set a planned date. This is the date on which your release will go live.
  4. Click on Save.

Once you have created your release, the below visual page will be displayed:

Creating a Feature Branch out of a Different Branch (Not Main Branch)

In the Advanced section, you can include a branch which will be used as the source branch to create feature branches. In previous Copado releases, the main branch was always taken by default. Now, it is the default branch, but it is possible to change it.

There is also a field in the release called Base Branch, where users can check the branch being used to create the feature branch. For more information about the fields included in a release, please visit our article Release Overview.

Version Tagging

Adding a version to your release helps you better track the events when new changes are delivered into production. You can have a better version control of your releases.

If you create a new release, you can create new values which will apply (1, 1.1, 1.0.1) to your release. The Major value is selected by default.

From the Release Detail page, click on Set Version. The following page will let you select your release version:

If the previous version is set as Status = Released, the version values will be automatically calculated to make the version assignment easier.

If your version number has a prefix and/or suffix  (e.g. "v3.43.64-SUMMER"), the following version will include the texts provided and will calculate the next number for the release:

How did we do?