Skip to content

OSDOCS-20088: Compliance Operator 1.9.1 z-stream release notes#113004

Merged
lahinson merged 1 commit into
openshift:mainfrom
GroceryBoyJr:co-191z
Jun 18, 2026
Merged

OSDOCS-20088: Compliance Operator 1.9.1 z-stream release notes#113004
lahinson merged 1 commit into
openshift:mainfrom
GroceryBoyJr:co-191z

Conversation

@GroceryBoyJr

@GroceryBoyJr GroceryBoyJr commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

@openshift-ci-robot

openshift-ci-robot commented Jun 9, 2026

Copy link
Copy Markdown

@GroceryBoyJr: This pull request references OSDOCS-20088 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 story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Version(s):

Issue: https://redhat.atlassian.net/browse/OSDOCS-20088

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 9, 2026
@openshift-ci openshift-ci Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jun 9, 2026
@ocpdocs-previewbot

ocpdocs-previewbot commented Jun 9, 2026

Copy link
Copy Markdown

@GroceryBoyJr

Copy link
Copy Markdown
Contributor Author

/assign @yuumasato
/assign @Vincent056
/assign @Anna-Koudelkova
/assign @taimurhafeez

@GroceryBoyJr

Copy link
Copy Markdown
Contributor Author

Hello @yuumasato @Vincent056 @Anna-Koudelkova @taimurhafeez asking for your review please. NOTE: I included the "enhancement" section in case you add any enhancements. If there are none for this z-stream release, let me know and I will remove that section.

@taimurhafeez taimurhafeez left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 10, 2026
Comment thread modules/compliance-rn-1-9-1.adoc Outdated
Comment thread modules/compliance-rn-1-9-1.adoc Outdated
Comment thread modules/compliance-rn-1-9-1.adoc Outdated
@Anna-Koudelkova

Copy link
Copy Markdown

Sorry for the confusion about what makes it into the CO 1.9.1. and what not - the process has some organic development traits and it is hard for us to keep track as well.
The other thing I have found in yesterdays PM/engineering notes is a note to "Add to RN that support RHCOS 10 is under development. Some rules may still fail." - I suppose RN stands for Release Notes?

@openshift-ci openshift-ci Bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jun 10, 2026
@GroceryBoyJr

Copy link
Copy Markdown
Contributor Author

@Anna-Koudelkova If you get a Jira for adding RHCOS10 support and it comes to pass, I'm glad to add it! Standing by to see what happens.

Comment thread modules/compliance-rn-1-9-1.adoc Outdated
@GroceryBoyJr GroceryBoyJr force-pushed the co-191z branch 3 times, most recently from 769e6db to 923df51 Compare June 18, 2026 11:44
@openshift-ci openshift-ci Bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jun 18, 2026
@GroceryBoyJr GroceryBoyJr force-pushed the co-191z branch 3 times, most recently from e79bea7 to b1f3f61 Compare June 18, 2026 12:14
Comment thread modules/compliance-rn-1-9-1.adoc Outdated
@lahinson lahinson added merge-review-in-progress Signifies that the merge review team is reviewing this PR and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Jun 18, 2026
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Jun 18, 2026
@openshift-ci

openshift-ci Bot commented Jun 18, 2026

Copy link
Copy Markdown

New changes are detected. LGTM label has been removed.

@lahinson lahinson left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@GroceryBoyJr A couple grammar nits and one question for you. When you're ready, ping me and I'll merge it.

Comment thread modules/compliance-rn-1-9-1.adoc Outdated
Comment thread modules/compliance-rn-1-9-1.adoc
Add release notes for Compliance Operator 1.9.1 with bug fixes for
CMP-4283, CMP-4323, CMP-4313, CMP-4333, and CMP-4349.

Co-authored-by: Cursor <cursoragent@cursor.com>

@lahinson lahinson left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM for merging. Will merge as soon as tests pass.

@GroceryBoyJr

Copy link
Copy Markdown
Contributor Author

@lahinson I've made the updates, thank you!

@openshift-ci

openshift-ci Bot commented Jun 18, 2026

Copy link
Copy Markdown

@GroceryBoyJr: all tests passed!

Full PR test history. Your PR dashboard.

Details

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.

@lahinson lahinson merged commit b5d76c7 into openshift:main Jun 18, 2026
2 checks passed
@lahinson

Copy link
Copy Markdown
Contributor

/cherrypick enterprise-4.20

@lahinson

Copy link
Copy Markdown
Contributor

/cherrypick enterprise-4.21

@lahinson

Copy link
Copy Markdown
Contributor

/cherrypick enterprise-4.22

@lahinson

Copy link
Copy Markdown
Contributor

/cherrypick enterprise-5.0

@openshift-cherrypick-robot

Copy link
Copy Markdown

@lahinson: new pull request created: #113647

Details

In response to this:

/cherrypick enterprise-4.20

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 kubernetes-sigs/prow repository.

@openshift-cherrypick-robot

Copy link
Copy Markdown

@lahinson: new pull request created: #113648

Details

In response to this:

/cherrypick enterprise-4.21

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 kubernetes-sigs/prow repository.

@openshift-cherrypick-robot

Copy link
Copy Markdown

@lahinson: new pull request created: #113649

Details

In response to this:

/cherrypick enterprise-4.22

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 kubernetes-sigs/prow repository.

@openshift-cherrypick-robot

Copy link
Copy Markdown

@lahinson: new pull request created: #113650

Details

In response to this:

/cherrypick enterprise-5.0

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 kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.20 branch/enterprise-4.21 branch/enterprise-4.22 branch/enterprise-5.0 jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. merge-review-in-progress Signifies that the merge review team is reviewing this PR qe-approved Signifies that QE has signed off on this PR size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants