CMP-4602: Update version to 1.10.0-dev in Makefile and manifests for development - #1351
Conversation
Master sat at 1.8.0-dev (previous 1.7.1) through the whole 1.9 cycle. Bump to 1.10.0-dev via 'make update-version-numbers' and point the upgrade chain at the latest release: PREVIOUS_VERSION=1.9.2, 'replaces: compliance-operator.v1.9.2' (was the long-stale v1.7.1), bundle regenerated with 'make bundle'. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
@Vincent056: This pull request references CMP-4602 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target either version "5.1.0." or "openshift-5.1.0.", but it targets "compliance-operator-1.10.0" instead. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
🤖 To deploy this PR, run the following command: |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: taimurhafeez, Vincent056 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm |
Master's version metadata sat at 1.8.0-dev (previous 1.7.1) through the entire 1.9 cycle — the dev bundle's CSV still said
replaces: compliance-operator.v1.7.1, so upgrade metadata against the actual 1.9.x releases was stale.Following the release-1.9 recipe (
Bump version to v1.9.2, using the #1325make update-version-numbersautomation):VERSION=1.10.0-dev(master convention:<next>.0-dev, cf.Update version to 1.8.0-dev...after 1.7.1) across version.Makefile, version/version.go, image labels (operator label was still1.7.1), base CSV, catalog preamble,bundle.openshift.Dockerfile(CO_NEW_VERSION)PREVIOUS_VERSION=1.9.2→replaces: compliance-operator.v1.9.2,CO_OLD_VERSION=1.9.2— one manual correction on top of the automation, which would have chained to the never-released 1.8.0-devmake bundleregenerated; operator-sdk bundle validation passes; every hunk is a pure version string🤖 Generated with Claude Code