Skip to content

[release-4.21] NO-JIRA: Remove (commented) WASM mentions #1888

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
openshift-merge-bot merged 1 commit into from
Jan 22, 2026
Merged

[release-4.21] NO-JIRA: Remove (commented) WASM mentions #1888

openshift-merge-bot merged 1 commit into from
Jan 22, 2026
+1 −16

Conversation

@ravanelli
Copy link
Member

@ravanelli ravanelli commented Jan 15, 2026

  • WASM support is no longer available in RHEL 9.8 and RHEL 10.0/10.1/10.2. Remove the corresponding extension mentions from RHCOS.

@ravanelli
COS-3840: Remove WASM mentions
cb03670 
- WASM support is no longer available in RHEL
  9.8 and RHEL 10.0/10.1/10.2. Remove the
  corresponding extension mentions from RHCOS.

Signed-off-by: Renata Ravanelli <rravanel@redhat.com>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 15, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 15, 2026 •
edited by openshift-ci bot
Loading

@ravanelli: This pull request references COS-3840 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target either version "4.21." or "openshift-4.21.", but it targets "openshift-4.22" instead.

Details

In response to this:

  • WASM support is no longer available in RHEL 9.8 and RHEL 10.0/10.1/10.2. Remove the corresponding extension mentions from RHCOS.

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 requested review from HuijingHei and c4rt0 January 15, 2026 12:46
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 15, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 15, 2026

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

marmijo
marmijo approved these changes Jan 15, 2026
View reviewed changes
Copy link
Contributor

@marmijo marmijo left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 15, 2026
travier
travier approved these changes Jan 20, 2026
View reviewed changes
Copy link
Member

@travier travier left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 20, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: marmijo, ravanelli, travier

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:
  • OWNERS [marmijo,ravanelli,travier]

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

@travier
Copy link
Member

travier commented Jan 22, 2026

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jan 22, 2026
@travier travier changed the title [release-4.21] COS-3840: Remove WASM mentions [release-4.21] NO-JIRA: Remove WASM mentions Jan 22, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 22, 2026

@ravanelli: This pull request explicitly references no jira issue.

Details

In response to this:

  • WASM support is no longer available in RHEL 9.8 and RHEL 10.0/10.1/10.2. Remove the corresponding extension mentions from RHCOS.

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.

@travier travier changed the title [release-4.21] NO-JIRA: Remove WASM mentions [release-4.21] NO-JIRA: Remove (commented) WASM mentions Jan 22, 2026
@travier travier added verified Signifies that the PR passed pre-merge verification criteria jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jan 22, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit e8f5a55 into openshift:release-4.21 Jan 22, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@travier travier travier approved these changes

@c4rt0 c4rt0 Awaiting requested review from c4rt0

@HuijingHei HuijingHei Awaiting requested review from HuijingHei

+1 more reviewer

@marmijo marmijo marmijo approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@marmijo marmijo

@travier travier

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@ravanelli @openshift-ci-robot @travier @marmijo