release: changes to publish 0.10.0 in operator hub #453
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
portersrc
changed the title
Updated the operator hub bundle for the 0.10.0 release. First bumped VERSION in Makefile then the new bundle was generated as: ``` $ make bundle IMG=quay.io/confidential-containers/operator:v0.10.0 ``` Signed-off-by: Chris Porter <porter@ibm.com>
portersrc
force-pushed
the
update-operator-bundle
branch
from
fa26515
to
fca91a3
Compare
wainersm
approved these changes
Sep 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I submitted the k8s-operatorhub/community-operators#5081 to publish 0.10.0 bundle in operator hub. After it is merged, coco's operator landing page in hub should get updated (see https://operatorhub.io/operator/cc-operator).
Here I'm sending the changes I did to publish it.