Skip to content

Encourage publishing catalog resources via CI job

Fabio Pitino requested to merge docs/fp-release-resources-via-release-keyword into master

What does this MR do and why?

Related to Docs: Update the docs to reflect the recommende... (#429271 - closed)

In this MR we encourage publishing catalog resources via CI job and remove entirely the possibility to publish versions using the create release UI form. In the upcoming months we will change the release-cli to collect metadata about components and publish the newly created release as a separate operation.

By using release keyword (an in turn release-cli tool) now we will greatly minimize UX impacts when we change the way we publish catalog resources later. A great advantage of this is also the fact that users see the benefit of testing the components before publishing the new released tag in the Catalog.

Screenshots or screen recordings

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

Before After

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