Skip to content

Release v1.0.13#1057

Closed
rcampos2029 wants to merge 1 commit intoopenshift-online:mainfrom
rcampos2029:release_1.0.13
Closed

Release v1.0.13#1057
rcampos2029 wants to merge 1 commit intoopenshift-online:mainfrom
rcampos2029:release_1.0.13

Conversation

@rcampos2029
Copy link
Copy Markdown
Collaborator

@rcampos2029 rcampos2029 commented Mar 24, 2026

@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Mar 24, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rcampos2029

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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 24, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 24, 2026

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: 383cab4b-85c6-496e-9479-d53ac4ae4a32

📥 Commits

Reviewing files that changed from the base of the PR and between a64d86e and c9b8a6d.

📒 Files selected for processing (2)
  • CHANGES.md
  • pkg/info/info.go
✅ Files skipped from review due to trivial changes (2)
  • pkg/info/info.go
  • CHANGES.md

Walkthrough

Bumped package version to 1.0.13 and added a new release entry in CHANGES.md documenting: default ingress excluded namespace selectors (day-1/day-2), cluster describe output including channel, new kubeletconfig describe/create/edit commands, and ability to clear excluded namespace selectors.

Changes

Cohort / File(s) Summary
Changelog
CHANGES.md
Added a new release section for v1.0.13 (Mar 23 2026) with five bullet entries describing ingress excluded namespace selectors (day-1/day-2), cluster describe channel inclusion, kubeletconfig describe/create/edit commands, and clearing excluded namespace selectors.
Version Constant
pkg/info/info.go
Updated exported Version constant from 1.0.12 to 1.0.13.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Release v1.0.13' directly matches the pull request's primary purpose of releasing version 1.0.13, as evidenced by the version bump in pkg/info/info.go and the changelog additions in CHANGES.md.
Description check ✅ Passed The description provides a detailed list of five features and fixes included in the v1.0.13 release, which directly corresponds to the changes documented in CHANGES.md and aligns with the pull request objectives.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

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

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

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

🧹 Nitpick comments (1)
CHANGES.md (1)

6-6: Minor date discrepancy.

The changelog shows Mar 23 2026, but this PR was created on March 24, 2026. Consider verifying whether the release date should be March 23 or 24 for consistency.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@CHANGES.md` at line 6, Edit the changelog header "## 1.0.13 Mar 23 2026" in
CHANGES.md to use the correct release date (e.g., change "Mar 23 2026" to "Mar
24 2026") or otherwise confirm and set the intended date for the 1.0.13 entry so
the header exactly reads the correct release date.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@CHANGES.md`:
- Line 6: Edit the changelog header "## 1.0.13 Mar 23 2026" in CHANGES.md to use
the correct release date (e.g., change "Mar 23 2026" to "Mar 24 2026") or
otherwise confirm and set the intended date for the 1.0.13 entry so the header
exactly reads the correct release date.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 7a29921f-f778-48e5-8344-e1ba433b56e6

📥 Commits

Reviewing files that changed from the base of the PR and between f1347f6 and a64d86e.

📒 Files selected for processing (2)
  • CHANGES.md
  • pkg/info/info.go

- OCM-21285 | feat: day-1 support for default ingress excluded namespace selectors
- OCM-22568 | fix: show channel field in cluster describe output (openshift-online#1041)
- OCM-21286 | feat: day-2 support for ingress excluded namespace selectors
- OCM-22804 | feat: add describe, create, and edit kubeletconfig commands (openshift-online#1042)
- OCM-22964 | fix: support clearing excluded namespace selectors
@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 3, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Apr 3, 2026

PR needs rebase.

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.

@rcampos2029 rcampos2029 closed this Apr 3, 2026
@rcampos2029 rcampos2029 deleted the release_1.0.13 branch April 3, 2026 15:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant