بنقرة واحدة
version-update
// Updates the operator version number across all required files and regenerates the bundle. Use when bumping the version for a release or when the user asks to update, bump, or change the version number.
// Updates the operator version number across all required files and regenerates the bundle. Use when bumping the version for a release or when the user asks to update, bump, or change the version number.
| name | version-update |
| description | Updates the operator version number across all required files and regenerates the bundle. Use when bumping the version for a release or when the user asks to update, bump, or change the version number. |
| disable-model-invocation | true |
Update the version in two files. They must all match.
name field includes a v prefix (e.g., lightspeed-operator.v1.0.8)version field does NOT have a prefix (e.g., 1.0.8)1. bundle.Dockerfile — Bundle container labels (lines 63 and 66)
LABEL release=X.Y.Z
# ...
LABEL version=X.Y.Z
2. bundle/manifests/lightspeed-operator.clusterserviceversion.yaml — CSV metadata
Line 58:
name: lightspeed-operator.vX.Y.Z
Line 715:
version: X.Y.Z
Note: Line numbers are approximate and may shift. Use search to locate:
name: lightspeed-operator.v (around line 58)version: near the end of the file (around line 715)# Update both LABEL release and LABEL version
sed -i '' 's/^LABEL release=.*/LABEL release=X.Y.Z/' bundle.Dockerfile
sed -i '' 's/^LABEL version=.*/LABEL version=X.Y.Z/' bundle.Dockerfile
Or manually edit lines 63 and 66.
Line ~58 (name field with v prefix):
name: lightspeed-operator.vX.Y.Z
Line ~715 (version field WITHOUT prefix):
version: X.Y.Z
After updating both files, regenerate the bundle:
make bundle
Or use the script:
hack/update_bundle.sh -v X.Y.Z
This ensures all generated files are consistent with the new version.
git diff bundle.Dockerfile bundle/manifests/
Confirm:
bundle.Dockerfile has release=X.Y.Z and version=X.Y.Zname field: lightspeed-operator.vX.Y.Z (with v prefix)version field: X.Y.Z (without prefix)git add bundle.Dockerfile bundle/
git commit -m "Bump version to X.Y.Z"
bundle.Dockerfile updated (lines 63, 66)bundle/manifests/lightspeed-operator.clusterserviceversion.yaml name updated (line ~58, with v prefix)bundle/manifests/lightspeed-operator.clusterserviceversion.yaml version updated (line ~715, without prefix)make bundle or hack/update_bundle.sh❌ Forgetting the v prefix in CSV name field
❌ Adding a v prefix to CSV version field
❌ Updating only one file
❌ Not regenerating the bundle after changes
❌ Mismatched version numbers between files
Find code duplication in the codebase. Supports two modes - scoped to current branch changes or a full codebase sweep. Use when the user asks to find duplicated code, copy-paste, repeated patterns, or wants to deduplicate before a PR.
Find functions with high cyclomatic complexity, excessive length, or too many parameters. Use when the user asks to find complex code, complexity hotspots, refactoring candidates, or wants to improve code maintainability.
Find unused functions, types, constants, imports, and unreachable code paths. Use when the user asks to find dead code, unused code, cleanup candidates, or wants to reduce codebase size.
Performs a strict clean rebase of a feature branch onto main with minimal conflict resolution and full validation. Use when the user asks to rebase carefully, avoid extra branches, avoid exploratory edits, and run make test and make lint until green.
Review PR with structured approach covering architecture, naming, patterns, and critical questions
After a code change, find affected tests, update them to match new behavior, then guide the user to run validation. Use when the user has made or asked for a code change and wants to make sure nothing is broken.