Skip to content

Add note to OCM v1.3.1 about Policy v0.19.0 - #560

Open
JustinKuli wants to merge 1 commit into
open-cluster-management-io:mainfrom
JustinKuli:policy-0.19.0-note
Open

Add note to OCM v1.3.1 about Policy v0.19.0#560
JustinKuli wants to merge 1 commit into
open-cluster-management-io:mainfrom
JustinKuli:policy-0.19.0-note

Conversation

@JustinKuli

@JustinKuli JustinKuli commented Jun 3, 2026

Copy link
Copy Markdown
Member

The rest of the docs don't seem to specify a version for the Policy addons, but it would be nice to add the newest release to the OCM release note, just for awareness.

Summary by CodeRabbit

  • Documentation
    • Added an "Add-on Components" subsection to the release notes clarifying that add-ons release independently.
    • Documented the policy add-on stack at v0.19.0, including changelog links and additional PR links for specific policy components.

@netlify

netlify Bot commented Jun 3, 2026

Copy link
Copy Markdown

Deploy Preview for open-cluster-management ready!

Name Link
🔨 Latest commit 50873f9
🔍 Latest deploy log https://app.netlify.com/projects/open-cluster-management/deploys/6a2094c857543000080dbfe5
😎 Deploy Preview https://deploy-preview-560--open-cluster-management.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@openshift-ci
openshift-ci Bot requested review from dhaiducek and xuezhaojun June 3, 2026 19:36
@openshift-ci

openshift-ci Bot commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: JustinKuli
Once this PR has been reviewed and has the lgtm label, please assign dhaiducek for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

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

@coderabbitai

coderabbitai Bot commented Jun 3, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 991ecb23-86f0-4d57-87b3-583bec61bdb5

📥 Commits

Reviewing files that changed from the base of the PR and between 23976fd and 50873f9.

📒 Files selected for processing (1)
  • content/en/docs/release/_index.md
🚧 Files skipped from review as they are similar to previous changes (1)
  • content/en/docs/release/_index.md

Walkthrough

Release documentation for OCM v1.3.1 is updated with a new "Add-on Components" subsection listing the policy add-on stack (v0.19.0) and providing changelog links for each policy-related component.

Changes

Release Documentation Update

Layer / File(s) Summary
Policy Components documentation
content/en/docs/release/_index.md
Policy Components subsection added to v1.3.1 release notes enumerating the policy add-on stack v0.19.0 and linking component changelogs.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Suggested labels

lgtm, approved

Suggested reviewers

  • xuezhaojun
  • dhaiducek
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly and clearly summarizes the main change: adding a note about Policy v0.19.0 to OCM v1.3.1 release documentation.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Comment thread content/en/docs/release/_index.md Outdated
Comment on lines +26 to +35
### 🧩 Policy Components

Policy add-ons release on their own schedule, independent of OCM core. The current policy stack is **v0.19.0**:

- **config-policy-controller** v0.19.0 [changelog](https://github.com/open-cluster-management-io/config-policy-controller/releases/tag/v0.19.0)
- **governance-policy-framework-addon** v0.19.0 [changelog](https://github.com/open-cluster-management-io/governance-policy-framework-addon/releases/tag/v0.19.0)
- **governance-policy-propagator** v0.19.0 [changelog](https://github.com/open-cluster-management-io/governance-policy-propagator/releases/tag/v0.19.0)
- **governance-policy-addon-controller** v0.19.0 [changelog](https://github.com/open-cluster-management-io/governance-policy-addon-controller/releases/tag/v0.19.0)
- **policy-generator-plugin** v0.19.0 [changelog](https://github.com/open-cluster-management-io/policy-generator-plugin/releases/tag/v0.19.0)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We'll hopefully have more add-ons that could be added to the releases here. Since we're setting precedence, I propose making the header and note about release independence more generic and then creating a list with sub-bullets, version, and release date.

Are there any release notes we'd want to add to the list aside from changelogs? And I'm also not sure how we're going to handle versioning for the async clusteradm updates. Might need more input on that. I wonder if a v1.3.1-1 or even v1.3.1-1-policy tag might do it...

Suggested change
### 🧩 Policy Components
Policy add-ons release on their own schedule, independent of OCM core. The current policy stack is **v0.19.0**:
- **config-policy-controller** v0.19.0 [changelog](https://github.com/open-cluster-management-io/config-policy-controller/releases/tag/v0.19.0)
- **governance-policy-framework-addon** v0.19.0 [changelog](https://github.com/open-cluster-management-io/governance-policy-framework-addon/releases/tag/v0.19.0)
- **governance-policy-propagator** v0.19.0 [changelog](https://github.com/open-cluster-management-io/governance-policy-propagator/releases/tag/v0.19.0)
- **governance-policy-addon-controller** v0.19.0 [changelog](https://github.com/open-cluster-management-io/governance-policy-addon-controller/releases/tag/v0.19.0)
- **policy-generator-plugin** v0.19.0 [changelog](https://github.com/open-cluster-management-io/policy-generator-plugin/releases/tag/v0.19.0)
### 🧩 Add-on Components
**NOTE:** Add-ons release independently from OCM core.
- **Policy Add-on, `v0.19.0`, 03 Jun 2026**
- **config-policy-controller** v0.19.0 [changelog](https://github.com/open-cluster-management-io/config-policy-controller/releases/tag/v0.19.0)
- **governance-policy-framework-addon** v0.19.0 [changelog](https://github.com/open-cluster-management-io/governance-policy-framework-addon/releases/tag/v0.19.0)
- **governance-policy-propagator** v0.19.0 [changelog](https://github.com/open-cluster-management-io/governance-policy-propagator/releases/tag/v0.19.0)
- **governance-policy-addon-controller** v0.19.0 [changelog](https://github.com/open-cluster-management-io/governance-policy-addon-controller/releases/tag/v0.19.0)
- **policy-generator-plugin** v0.19.0 [changelog](https://github.com/open-cluster-management-io/policy-generator-plugin/releases/tag/v0.19.0)

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I like the idea of making the section for all addons! Sounds like the pattern could be that addons add their releases under the latest OCM release they've been tested with? Ideally they don't get added to older releases, unless necessary.

Regarding the format, I'm not sure that nested bullets will always be rendered correctly, so personally I think the heading + bullets format that the highlights section of 1.3.0 used might be more consistent. Let me try that out, with some details of the new release.

Regarding the clusteradm update, I don't really have a preference. Adding an additional version field seems like a hassle or a point of confusion. But changing what is already in v1.3.1 is also confusing.

Signed-off-by: Justin Kulikauskas <jkulikau@redhat.com>
@JustinKuli
JustinKuli force-pushed the policy-0.19.0-note branch from 23976fd to 50873f9 Compare June 3, 2026 20:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants