Add the component_metadata.yaml file to track codeflare-operator rele…

…ase version
opendatahub-io · Jan 7, 2025 · 2202372 · 2202372
1 parent b868c67
commit 2202372
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 0 deletions.
diff --git a/README.md b/README.md
@@ -114,6 +114,7 @@ For ODH tests additional environment variables are needed:
 6. In ODH/CFO verify that the [Build and Push action](https://github.com/opendatahub-io/codeflare-operator/actions/workflows/build-and-push.yaml) was triggered and ran successfully.
 7. Make sure that release automation created a PR updating CodeFlare SDK version in [ODH Notebooks repository](https://github.com/opendatahub-io/notebooks). Make sure the PR gets merged.
 8. Run [ODH CodeFlare Operator release workflow](https://github.com/opendatahub-io/codeflare-operator/actions/workflows/odh-release.yml) to produce ODH CodeFlare Operator release.
+9. Ensure that the version details in the `config/component_metadata.yaml` file are updated to reflect the latest CodeFlare Operator release version
 
 ### Releases involving part of the stack
 

diff --git a/config/component_metadata.yaml b/config/component_metadata.yaml
@@ -0,0 +1,4 @@
+releases:
+  - name: codeflare-operator
+    version: 1.12.0
+    repoUrl: https://github.com/project-codeflare/codeflare-operator