Skip to content

CMP-4602: Update version to 1.10.0-dev in Makefile and manifests for development - #1351

Merged
taimurhafeez merged 1 commit into
ComplianceAsCode:masterfrom
Vincent056:master-version-1.10.0
Aug 18, 2026
Merged

CMP-4602: Update version to 1.10.0-dev in Makefile and manifests for development#1351
taimurhafeez merged 1 commit into
ComplianceAsCode:masterfrom
Vincent056:master-version-1.10.0

Conversation

@Vincent056

Copy link
Copy Markdown

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 #1325 make update-version-numbers automation):

  • 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 still 1.7.1), base CSV, catalog preamble, bundle.openshift.Dockerfile (CO_NEW_VERSION)
  • PREVIOUS_VERSION=1.9.2replaces: 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-dev
  • make bundle regenerated; operator-sdk bundle validation passes; every hunk is a pure version string

🤖 Generated with Claude Code

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 Vincent056 added this to the 1.10.0 milestone Aug 18, 2026
@openshift-ci
openshift-ci Bot requested review from mrogers950 and rhmdnd August 18, 2026 15:28
@Vincent056 Vincent056 changed the title Update version to 1.10.0-dev in Makefile and manifests for development CMP-4602: Update version to 1.10.0-dev in Makefile and manifests for development Aug 18, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Collaborator

@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.

Details

In response to this:

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 #1325 make update-version-numbers automation):

  • 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 still 1.7.1), base CSV, catalog preamble, bundle.openshift.Dockerfile (CO_NEW_VERSION)
  • PREVIOUS_VERSION=1.9.2replaces: 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-dev
  • make bundle regenerated; operator-sdk bundle validation passes; every hunk is a pure version string

🤖 Generated with Claude Code

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.

@github-actions

Copy link
Copy Markdown

🤖 To deploy this PR, run the following command:

make catalog-deploy CATALOG_IMG=ghcr.io/complianceascode/compliance-operator-catalog:1351-ba1837d8bb308c879e639e92a1de35a777dcf820

@openshift-ci

openshift-ci Bot commented Aug 18, 2026

Copy link
Copy Markdown

[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

Details Needs approval from an approver in each of these files:
  • OWNERS [Vincent056,taimurhafeez]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@taimurhafeez

Copy link
Copy Markdown
Collaborator

/lgtm

@taimurhafeez
taimurhafeez merged commit 367878a into ComplianceAsCode:master Aug 18, 2026
17 of 28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants