Skip to content

Latest commit

 

History

History
39 lines (25 loc) · 2.01 KB

RELEASE.md

File metadata and controls

39 lines (25 loc) · 2.01 KB
Raw

Release

Process

  1. Pick a stable (released) version “v0.X.Y” of the operand known to be compatible with operator’s image for “v0.W.Z”; if needed, make a release of the operand first.

  2. Run the GHA Release operator; make sure to fill all the fields:

    • Branch containing the release workflow file – default: main
    • Commit SHA or branch name of the operator to release – usually: main
    • Operator version to release (without prefix) – i.e. 0.W.Z
    • Limitador version the operator enables installations of (without prefix) – i.e. 0.X.Y
    • If the release is a prerelease

  3. Verify that the build release tag workflow is triggered and completes for the new tag

  4. Verify the new version can be installed from the catalog image, see Verify OLM Deployment

  5. Release to the community operator index catalogs.

Community Operator Index Catalogs

Open a PR on each index catalog (example | docs).

The usual steps are:

  1. Start a new branch named limitador-operator-v0.W.Z

  2. Create a new directory operators/limitador-operator/0.W.Z containing:

    • Copy the bundle files from github.com/kuadrant/limitador-operator/tree/v0.W.Z/bundle
    • Copy github.com/kuadrant/limitador-operator/tree/v0.W.Z/bundle.Dockerfile with the proper fix to the COPY commands (i.e. remove /bundle from the paths)