Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance the "[bot] bump payload versions" to update the "clusterserviceversion" template #2032

Closed
vdemeester opened this issue Feb 26, 2024 · 1 comment · Fixed by #2076
Closed
Assignees
Labels
area/automation Issues that are related to automation aspects of the website or other projects. kind/feature Categorizes issue or PR as related to a new feature.

Comments

@vdemeester
Copy link
Member

As of today, we update version based on component release automatically using an internal tooling and some workflow (see an example here.

One enhancement would be to make sure we keep "reference" to that version up-to-date. The main example to this is the openshift-pipelines-operator-rh.clusterversion.template.yaml that displays information about component in the OpenShift UI (for example).

The tool should be able to handle this, and keep that part up-to-date, so we don't have to manually change those.

@vdemeester vdemeester added kind/feature Categorizes issue or PR as related to a new feature. area/automation Issues that are related to automation aspects of the website or other projects. labels Feb 26, 2024
@vdemeester
Copy link
Member Author

cc @tektoncd/operator-maintainers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/automation Issues that are related to automation aspects of the website or other projects. kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant