Skip to content

OSDOCS-17043: revert erroneously propagated deprecation#107812

Open
jeana-redhat wants to merge 1 commit intoopenshift:enterprise-4.18from
jeana-redhat:OSDOCS-17043-revert-deprecation
Open

OSDOCS-17043: revert erroneously propagated deprecation#107812
jeana-redhat wants to merge 1 commit intoopenshift:enterprise-4.18from
jeana-redhat:OSDOCS-17043-revert-deprecation

Conversation

@jeana-redhat
Copy link
Contributor

@jeana-redhat jeana-redhat commented Mar 3, 2026

Version(s):
4.16-4.18

Issue:
OSDOCS-17043

Link to docs preview:

QE review:
N/A

Additional information:
Discovered while manually cherrypicking of #103103 into 4.19 that the manual picks for 4.16-4.18 propagated a 4.20+ deprecation notice (ref: #99963) into earlier content as part of merge conflict resolution. This reverts that change to the appropriate pre-4.20 state. Confirmed dep status as 4.20+ with @skopacz1 🙇

@jeana-redhat jeana-redhat added this to the Continuous Release milestone Mar 3, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 3, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 3, 2026

@jeana-redhat: This pull request references OSDOCS-17043 which is a valid jira issue.

Details

In response to this:

Version(s):
4.16-4.18

Issue:
OSDOCS-17043

Link to docs preview:

QE review:
N/A

Additional information:
Discovered while manually cherrypicking of #103103 into 4.19 that the manual picks for 4.16-4.18 propagated a 4.20+ deprecation notice (ref: #99963) into earlier content as part of merge conflict resolution. This reverts that change to the appropriate pre-4.20 state. Confirmed dep status as 4.20+ with @skopacz1 🙇

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.

@jeana-redhat jeana-redhat added the merge-review-needed Signifies that the merge review team needs to review this PR label Mar 3, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 3, 2026

@jeana-redhat: This pull request references OSDOCS-17043 which is a valid jira issue.

Details

In response to this:

Version(s):
4.16-4.18

Issue:
OSDOCS-17043

Link to docs preview:

QE review:
N/A

Additional information:
Discovered while manually cherrypicking of #103103 into 4.19 that the manual picks for 4.16-4.18 propagated a 4.20+ deprecation notice (ref: #99963) into earlier content as part of merge conflict resolution. This reverts that change to the appropriate pre-4.20 state. Confirmed dep status as 4.20+ with @skopacz1 🙇

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/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Mar 3, 2026
@jeana-redhat jeana-redhat removed the merge-review-needed Signifies that the merge review team needs to review this PR label Mar 3, 2026
@jeana-redhat jeana-redhat force-pushed the OSDOCS-17043-revert-deprecation branch from 022d9d7 to f8e6e53 Compare March 3, 2026 15:53
@openshift-ci openshift-ci bot removed the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Mar 3, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 3, 2026

@jeana-redhat: This pull request references OSDOCS-17043 which is a valid jira issue.

Details

In response to this:

Version(s):
4.16-4.18

Issue:
OSDOCS-17043

Link to docs preview:

QE review:
N/A

Additional information:
Discovered while manually cherrypicking of #103103 into 4.19 that the manual picks for 4.16-4.18 propagated a 4.20+ deprecation notice (ref: #99963) into earlier content as part of merge conflict resolution. This reverts that change to the appropriate pre-4.20 state. Confirmed dep status as 4.20+ with @skopacz1 🙇

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 Mar 3, 2026
@openshift-ci
Copy link

openshift-ci bot commented Mar 3, 2026

@jeana-redhat: 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.

@jeana-redhat jeana-redhat self-assigned this Mar 3, 2026
@jeana-redhat jeana-redhat added the merge-review-needed Signifies that the merge review team needs to review this PR label Mar 3, 2026
@jeana-redhat jeana-redhat removed their assignment Mar 3, 2026
@skopacz1 skopacz1 added the merge-review-in-progress Signifies that the merge review team is reviewing this PR label Mar 3, 2026
Copy link
Contributor

@skopacz1 skopacz1 left a comment

Choose a reason for hiding this comment

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

LGTM

@skopacz1 skopacz1 added ok-to-merge and removed merge-review-in-progress Signifies that the merge review team is reviewing this PR merge-review-needed Signifies that the merge review team needs to review this PR labels Mar 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.16 branch/enterprise-4.17 branch/enterprise-4.18 jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. ok-to-merge 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