Skip to content
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.

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

DFBUGS-810: [release-4.17-compatibility] Fix 'cross-spawn' CVE #1746

Open
wants to merge 1 commit into
base: release-4.17-compatibility
Choose a base branch
from

Conversation

Copy link
Contributor

openshift-ci bot commented Nov 29, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SanjalKatiyar

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

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

@SanjalKatiyar SanjalKatiyar changed the title Fix 'cross-spawn' CVE [release-4.17-compatibility] Fix 'cross-spawn' CVE Nov 29, 2024
@SanjalKatiyar
Copy link
Collaborator Author

SanjalKatiyar commented Nov 29, 2024

/retitle DFBUGS-810: [release-4.17-compatibility] Fix 'cross-spawn' CVE

@openshift-ci openshift-ci bot changed the title [release-4.17-compatibility] Fix 'cross-spawn' CVE DFBUGS-810: [release-4.17-compatibility] Fix 'cross-spawn' CVE Nov 29, 2024
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid jira ticket of any type jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting labels Nov 29, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 29, 2024

@SanjalKatiyar: This pull request references [Jira Issue DFBUGS-810](https://issues.redhat.com//browse/DFBUGS-810), which is valid. The bug has been moved to the POST state.

2 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

In response to this:

#1695

https://issues.redhat.com/browse/DFBUGS-804
https://issues.redhat.com/browse/DFBUGS-810
https://issues.redhat.com/browse/DFBUGS-816

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.

Copy link
Contributor

openshift-ci bot commented Nov 29, 2024

@SanjalKatiyar: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/odf-console-e2e-aws 381c734 link true /test odf-console-e2e-aws

Full PR test history. Your PR dashboard.

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
approved jira/valid-bug Indicates that the 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants