Conversation
Signed-off-by: SequeI <asiek@redhat.com>
Review Summary by QodoRevert to tech preview version 0.1.0 across build and deployment configs
WalkthroughsDescription• Revert image version from 1.0.0 to 0.1.0 across all Tekton pipeline files • Update Dockerfile bundle to use tech-preview channel instead of stable • Change project maturity status to tech-preview in ClusterServiceVersion • Update VERSION variable in Makefile to 0.1.0-techpreview Diagramflowchart LR
A["Version 1.0.0"] -- "Downgrade to" --> B["Version 0.1.0"]
C["Stable Channel"] -- "Switch to" --> D["Tech-Preview Channel"]
B -- "Applied to" --> E["Tekton Pipelines"]
B -- "Applied to" --> F["Makefile"]
B -- "Applied to" --> G["ClusterServiceVersion"]
D -- "Applied to" --> H["Dockerfile Bundle"]
File Changes1. .tekton/model-validation-operator-agent-pull-request.yaml
|
Code Review by Qodo
|
JasonPowr
approved these changes
Apr 10, 2026
![qodo-code-review[bot]](https://avatars.githubusercontent.com/in/484649?s=60&v=4){kind=small}
Comment on lines
+68
to
+72
| maturity: tech-preview | ||
| minKubeVersion: 1.24.0 | ||
| provider: | ||
| name: Red Hat | ||
| version: 1.0.0 | ||
| version: 0.1.0-techpreview |
There was a problem hiding this comment.
1. Csv name/version mismatch 🐞 Bug ≡ Correctness
The base ClusterServiceVersion sets metadata.name to model-validation-operator.v0.1.0 while spec.version is 0.1.0-techpreview, making the CSV internally inconsistent and potentially invalid for OLM/operator-sdk validation.
Agent Prompt
### Issue description
The base CSV uses two different version strings: `metadata.name` embeds `v0.1.0` while `spec.version` is `0.1.0-techpreview`. OLM/`operator-sdk bundle validate` expects consistent CSV metadata, and this file is included in the manifests used for bundle generation.
### Issue Context
This CSV is a direct input into the bundle generation kustomize pipeline and is therefore part of what gets validated.
### Fix Focus Areas
- config/manifests/bases/model-validation-operator.clusterserviceversion.yaml[21-22]
- config/manifests/bases/model-validation-operator.clusterserviceversion.yaml[68-72]
### What to change
Choose one consistent version string and apply it to BOTH:
- `metadata.name: model-validation-operator.v<version>`
- `spec.version: <version>`
For example, either:
- keep `spec.version: 0.1.0` (and `metadata.name: ...v0.1.0`), relying on channel/maturity to indicate tech-preview; OR
- use `spec.version: 0.1.0-techpreview` and update `metadata.name` to `model-validation-operator.v0.1.0-techpreview`.
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.