Skip to content

ROX-35505: Patch release notes for 4.11.1#114492

Merged
kcarmichael08 merged 1 commit into
openshift:rhacs-docs-4.11from
kcarmichael08:4.11.1-release-notes
Jul 7, 2026
Merged

ROX-35505: Patch release notes for 4.11.1#114492
kcarmichael08 merged 1 commit into
openshift:rhacs-docs-4.11from
kcarmichael08:4.11.1-release-notes

Conversation

@kcarmichael08

@kcarmichael08 kcarmichael08 commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Version(s): 4.11

Issue: https://redhat.atlassian.net/browse/ROX-35505

Link to docs preview: https://114492--ocpdocs-pr.netlify.app/openshift-acs/latest/release_notes/411-release-notes#bug-fixes-in-version-4111_release-notes-411

QE review: ACS has no QE, approved by SME

  • QE has approved this change.

Additional information:

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 1, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 1, 2026

Copy link
Copy Markdown

@kcarmichael08: This pull request references ROX-35505 which is a valid jira issue.

Details

In response to this:

Version(s): 4.11

Issue: https://redhat.atlassian.net/browse/ROX-35505

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 openshift-ci Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jul 1, 2026
@ocpdocs-previewbot

ocpdocs-previewbot commented Jul 1, 2026

Copy link
Copy Markdown

🤖 Tue Jul 07 17:24:14 - Prow CI generated the docs preview:
https://114492--ocpdocs-pr.netlify.app
Complete list of updated preview URLs: artifacts/updated_preview_urls.txt

Comment thread modules/bug-fixes-in-version-4111.adoc Outdated
@kcarmichael08 kcarmichael08 force-pushed the 4.11.1-release-notes branch 2 times, most recently from 164630d to 60ac4cf Compare July 1, 2026 17:48
@kcarmichael08 kcarmichael08 added RHACS Label for RHACS related PRs that go in the rhacs-docs branch rhacs-docs-4.11 Label for PRs that apply to RHACS 4.11 labels Jul 1, 2026
@agantony

agantony commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Vale Linting Fixes Summary for PR #114492

This summary provides actionable fixes for Vale linting issues found in the files modified by PR #114492.


Simple Word Issues (RedHat.SimpleWords)

modules/bug-fixes-in-version-4111.adoc

  • Line 11:70 - 'multiple'

    • Current: "Scanner V4 could report the same vulnerability multiple times for a single component due to multiple entries in the OSV data source."
    • Suggested: "Scanner V4 could report the same vulnerability many times for a single component due to many entries in the OSV data source."
  • Line 19:114 - 'incorrect'

    • Current: "the {product-title-short} Helm chart versions in the mirror and GitHub repositories showed incorrect version strings."
    • Suggested: "the {product-title-short} Helm chart versions in the mirror and GitHub repositories showed wrong version strings."
  • Line 33:52 - 'incorrect'

    • Current: "golang.org/x/net/idna: Privilege escalation via incorrect Punycode label processing"
    • Suggested: "golang.org/x/net/idna: Privilege escalation via wrong Punycode label processing"
    • Note: Consider if "incorrect" is technically accurate here - security vulnerability descriptions may require precise technical terminology. If this is a direct quote from the CVE, it may be acceptable to keep "incorrect."

Passive Voice Issues (RedHat.PassiveVoice)

modules/bug-fixes-in-version-4111.adoc

  • Line 11:241 - 'is reported'

    • Current: "ensuring that each CVE is reported only once per component, reducing false positives and improving vulnerability report accuracy."
    • Suggested: "ensuring that Scanner V4 reports each CVE only once per component, reducing false positives and improving vulnerability report accuracy."
    • Alternative: "ensuring that the system reports each CVE only once per component, reducing false positives and improving vulnerability report accuracy."
  • Line 13:324 - 'is confirmed'

    • Current: "reducing false positives by not reporting vulnerabilities for packages where the product is confirmed to be 'not affected'."
    • Suggested: "reducing false positives by not reporting vulnerabilities for packages where Red{nbsp}Hat confirms the product as 'not affected'."
    • Alternative: "reducing false positives by not reporting vulnerabilities for packages where VEX data confirms the product as 'not affected'."
  • Line 15:177 - 'is resolved'

    • Current: "With this release, this issue is resolved."
    • Suggested: "This release resolves this issue."
    • Alternative: "This release fixes this issue."
  • Line 19:189 - 'been corrected'

    • Current: "With this release, the Helm chart versions have been corrected to display the proper version number."
    • Suggested: "This release corrects the Helm chart versions to display the proper version number."
    • Alternative: "This release updates the Helm chart versions to display the proper version number."

Summary

Total issues: 8 Vale linting violations across 2 rule types in 1 file

Breakdown:

  • Simple Word Issues: 3 instances
  • Passive Voice Issues: 5 instances

Recommended Actions:

  1. Simple Words: Replace "multiple" with "many" (2 instances) and "incorrect" with "wrong" (2 instances). For line 33, verify if "incorrect" is part of the official CVE description before changing.

  2. Passive Voice: Rewrite sentences to use active voice constructions. The most common pattern is changing "is/was/have been [verb]" to "[subject] [verb]" format. Most of these can be fixed by restructuring sentences to make the software or release the active subject.

  3. Priority: The passive voice issues are more impactful for readability and adherence to Red Hat style guidelines. Consider addressing these first.

@agantony agantony added the peer-review-done Signifies that the peer review team has reviewed this PR label Jul 6, 2026
@kcarmichael08 kcarmichael08 force-pushed the 4.11.1-release-notes branch 2 times, most recently from af05983 to 4b0d9d6 Compare July 7, 2026 12:57
@kcarmichael08 kcarmichael08 force-pushed the 4.11.1-release-notes branch from 4b0d9d6 to 08c8c1b Compare July 7, 2026 17:12
@openshift-ci

openshift-ci Bot commented Jul 7, 2026

Copy link
Copy Markdown

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

@kcarmichael08 kcarmichael08 merged commit 8d13e80 into openshift:rhacs-docs-4.11 Jul 7, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. peer-review-done Signifies that the peer review team has reviewed this PR RHACS Label for RHACS related PRs that go in the rhacs-docs branch rhacs-docs-4.11 Label for PRs that apply to RHACS 4.11 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.

5 participants