Skip to content

Latest commit

 

History

History
48 lines (38 loc) · 2.02 KB

RELEASE_WORKFLOW.md

File metadata and controls

48 lines (38 loc) · 2.02 KB

Release workflow

Releasing a new version involves publishing packages to the NPM public registry and creating a container image containing a stand-alone version of the UI app (see apps/assisted-ui). The release.yaml workflow contains the scripts for producing and publishing the final artifacts.

How JS libraries are selected for publishing by the CI

The library's package.json must contain the following section in order to be selected by the CI.

{
  "publishConfig": {
    "access": "public"
  }
}

There are 3 possible releases, driven by the suffix in the release name:

  • OCM - no suffix
  • CIM - suffix -cim
  • Chatbot - suffix -chatbot

Instructions

  1. Make sure you have been granted the maintaner role in the project settings.
  2. Create a new branch from master and name it following this pattern: releases/v<some-semver-string>-<optionally_a_suffix>.
  3. Draft a new release through GitHub's interface.
  4. Fill the form with the following details:
    1. Tag: v<some-semver-string>-<optionally_a_suffix>
    2. Target branch: releases/v<some-semver-string>-<optionally_a_suffix> (the same as in the previous step).
    3. Title: v<some-semver-string>-<optionally_a_suffix> (again, the same as in the previous step).
    4. Description: Generate the release notes automatically (recommended), or edit the field manually.

List of publicly available artifacts