Visitar URL original
OSDOCS-24080: Add 4.19.54 z-stream release notes by tedaveryredhat · Pull Request #123556 · openshift/openshift-docs · GitHub
Skip to content

OSDOCS-24080: Add 4.19.54 z-stream release notes - #123556

Open
tedaveryredhat wants to merge 1 commit into
openshift:enterprise-4.19from
tedaveryredhat:OSDOCS-24080
Open

tedaveryredhat wants to merge 1 commit into
openshift:enterprise-4.19from
tedaveryredhat:OSDOCS-24080

Conversation

@tedaveryredhat

Copy link
Copy Markdown
Contributor

Summary

Documented

  • None (advisory-only)

Skipped (not documented)

Key Reason
— No OCPBUGS keys in shipment image YAML

Jira RN text populated (pre-step)

No issues required RN text population (0 auto-closed, 0 CCFR rewritten, 0 copied from clone, 0 CCFR written).

Scope notes

  • Shipment YAML keys: 0
  • Advisory-only module with stock "no notable fixed issues" text
  • Issued date set to planned ship date from shipment MR (4 November 2026)

Test plan

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

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

openshift-ci-robot commented Oct 29, 2026 •

Copy link
Copy Markdown

@tedaveryredhat: This pull request references OSDOCS-24080 which is a valid jira issue.

Details

In response to this:

Summary

Documented

  • None (advisory-only)

Skipped (not documented)

Key Reason
— No OCPBUGS keys in shipment image YAML

Jira RN text populated (pre-step)

No issues required RN text population (0 auto-closed, 0 CCFR rewritten, 0 copied from clone, 0 CCFR written).

Scope notes

  • Shipment YAML keys: 0
  • Advisory-only module with stock "no notable fixed issues" text
  • Issued date set to planned ship date from shipment MR (4 November 2026)

Test plan

  • Title and issued date match access.redhat.com when published
  • Primary + companion 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 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 Oct 29, 2026
@openshift-ci

openshift-ci Bot commented Oct 29, 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 Oct 29, 2026
@tedaveryredhat
tedaveryredhat marked this pull request as ready for review October 29, 2026 14:42
@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 Oct 29, 2026
@ocpdocs-previewbot

Copy link
Copy Markdown

🤖 Thu Oct 29 14:51:33 - Prow CI generated the docs preview:

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

[id="zstream-4-19-54-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 Oct 29, 2026

Copy link
Copy Markdown

@tedaveryredhat: 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