The structure of the release-config.yaml file is certified automatically during the pipeline run. If the file does not conform to the schema, the pull request will fail with a detailed error message.

The file must use the following structure:

• The top-level key is catalog_templates, which contains a list of catalog update definitions.
• Each item in the list represents one catalog template and must include:
  • template_name: Name of the catalog template file located in the catalog-templates/ directory.
  • channels: List of channels to which the bundle should be released.

    For SemVer templates, valid values are: Fast, Stable, and Candidate.

  • replaces (optional): Specifies which bundle the new one replaces in the update graph. This is valid only for the basic templates.
  • skips (optional): A list of bundles to skip in the update graph. This is valid only for the basic templates.
  • skipRange (optional): A range indicating which bundle versions should be skipped. This is valid only for the basic templates.