Skip to content

OSDOCS-20910: Add 4.19.40 z-stream release notes - #116611

Open
bjahagir-OpenShift wants to merge 1 commit into
openshift:enterprise-4.19from
bjahagir-OpenShift:OSDOCS-20910
Open

OSDOCS-20910: Add 4.19.40 z-stream release notes#116611
bjahagir-OpenShift wants to merge 1 commit into
openshift:enterprise-4.19from
bjahagir-OpenShift:OSDOCS-20910

Conversation

@bjahagir-OpenShift

Copy link
Copy Markdown
Contributor

Summary

Documented

  • OCPBUGS-98388

Skipped (not documented)

Key Reason
OCPBUGS-79002 Release Note Not Required
OCPBUGS-80361 CVE-only
OCPBUGS-80366 CVE-only
OCPBUGS-81608 CVE-only
OCPBUGS-84285 CVE-only
OCPBUGS-88654 CVE-only
OCPBUGS-91617 CVE-only
OCPBUGS-94080 Release Note Not Required
OCPBUGS-99306 Internal

Scope notes

  • Shipment YAML keys: 10
  • Errata Fixes keys: n/a (errata not confirmed live)
  • Draft PR until advisory pages are verified on access.redhat.com

Test plan

  • Title and issued date match access.redhat.com
  • Primary + RPM advisory links correct
  • Vale clean on touched files

@openshift-ci-robot

openshift-ci-robot commented Jul 27, 2026

Copy link
Copy Markdown

@bjahagir-OpenShift: This pull request references OSDOCS-20910 which is a valid jira issue.

Details

In response to this:

Summary

Documented

  • OCPBUGS-98388

Skipped (not documented)

Key Reason
OCPBUGS-79002 Release Note Not Required
OCPBUGS-80361 CVE-only
OCPBUGS-80366 CVE-only
OCPBUGS-81608 CVE-only
OCPBUGS-84285 CVE-only
OCPBUGS-88654 CVE-only
OCPBUGS-91617 CVE-only
OCPBUGS-94080 Release Note Not Required
OCPBUGS-99306 Internal

Scope notes

  • Shipment YAML keys: 10
  • Errata Fixes keys: n/a (errata not confirmed live)
  • Draft PR until advisory pages are verified on access.redhat.com

Test plan

  • Title and issued date match access.redhat.com
  • Primary + RPM advisory links correct
  • Vale clean on touched files

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 Jul 27, 2026
@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 27, 2026
@openshift-ci

openshift-ci Bot commented Jul 27, 2026

Copy link
Copy Markdown

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci openshift-ci Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jul 27, 2026
@bjahagir-OpenShift
bjahagir-OpenShift marked this pull request as ready for review July 27, 2026 17:55
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 27, 2026
@ocpdocs-previewbot

Copy link
Copy Markdown

🤖 Mon Jul 27 18:05:32 - Prow CI generated the docs preview:

https://116611--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-19-release-notes.html

[id="zstream-4-19-40-updating_{context}"]
== Updating

To update an {product-title} 4.19 cluster to this latest release, see xref:../updating/updating_a_cluster/updating-cluster-cli.adoc#updating-cluster-cli[Updating a cluster using the CLI].

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).

@openshift-ci

openshift-ci Bot commented Jul 27, 2026

Copy link
Copy Markdown

@bjahagir-OpenShift: 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.

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

4 participants