-
Checkout your fork and make sure it's up-to-date with the
upstream
$ git remote -v origin [email protected]:<your account>/trivy-operator.git (fetch) origin [email protected]:<your account>/trivy-operator.git (push) upstream [email protected]:aquasecurity/trivy-operator.git (fetch) upstream [email protected]:aquasecurity/trivy-operator.git (push)
git pull -r git fetch upstream git merge upstream/main git push
-
Prepare release by creating the PR with the following changes
-
- Update the
version
property (if change automatically will release a new chart) - Update the
appVersion
property
- Update the
-
Update the
app.kubernetes.io/version
labels in the following files: -
Update static resources from Helm chart by running the mage target:
mage generate:manifests
-
In
mkdocs.yml
- Update the
extra.var.prev_git_tag
property - Update the
extra.var.chart_version
property
- Update the
-
-
Review and merge the PR (make sure all tests are passing)
-
Update your fork again
git pull -r git fetch upstream git merge upstream/main git push
-
Create an annotated git tag and push it to the
upstream
. This will trigger the.github/workflows/release.yaml
workflowgit tag -v0.23.0 -m 'Release v0.23.0' git push upstream v0.23.0
-
Verify that the
release
workflow has built and published the following artifacts- Trivy-operator container images published to DockerHub
docker.io/aquasec/trivy-operator:0.23.0
- Trivy-operator container images published to Amazon ECR Public Gallery
public.ecr.aws/aquasecurity/trivy-operator:0.23.0
- Trivy-operator container images published to GitHub Container Registry
ghcr.io/aquasecurity/trivy-operator:0.23.0
- Trivy-operator container images published to DockerHub
-
Submit trivy-operator Operator to OperatorHub and ArtifactHUB by opening the PR to the https://github.com/k8s-operatorhub/community-operators repository.