Skip to content

Clarify use of releases in versioning

What does this MR do and why?

Related to Support `@<release>` version when including com... (#390838 - closed)

This MR clarifies the use of releases in the catalog for a given project (pipeline module) and the use of @~latest version qualifier.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports

Loading