Skip to content

Latest commit

 

History

History
50 lines (40 loc) · 2.55 KB

release.md

File metadata and controls

50 lines (40 loc) · 2.55 KB
Raw

Release

  • Update Makefile variable VERSION to the appropiate release version. Allowed formats:
    • alpha: VERSION ?= 0.3.8-alpha.3 - Used for operator development before doing a final release
    • stable: VERSION ?= 0.3.8 - Used once alpha releases have been tested successfully
  • IMPORTANT: VERSION (having the -alpha suffix or not, must coincide with the original helm chart release, because it is used to download the original helm chart from Git Hub

Alpha

  • If it is an alpha release, execute the following target to create appropiate alpha bundle files:
make prepare-alpha-release
  • Then you can manually execute opetator, bundle and catalog build/push:
make docker-build
make docker-push
make bundle-publish

Stable

  • But if it is an stable release, execute the following target to create appropiate alpha and stable bundle files:
make prepare-stable-release
  • Then open a Pull Request, and a GitHub Action will automatically detect if it is new release or not, in order to create it by building/pushing new operator, bundle and catalog images, as well as creating a GitHub release draft.

OperatorHub.io

In order to make the latest release available to OperatorHub.io we need to create a bundle and open a PR in the community-operators repository.

To create a bundle first increment the VERSION in the Makefile as described above. Then run the following commands in the root of the repository:

make prepare-stable-release

Check the generated files in the bundle/ directory. If they look good add & commit them, open a PR against this repository. You can always use the OperatorHub.io/preview page to preview the generated CSV.

git status
git add .
git commit -s -m "chore: bump version xyz"
git push

Once the PR is merged we need create a pull request against the community-operators repository. there's a make target that does the heavy lifting for you:

make bundle-operatorhub

You then just need to push to your fork and open a PR against the community-operators repository. If you're a reviewer the PR gets merged automatically. The website needs some time 10-30 minutes to display the latest changes.