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.

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

DFBUGS-809: [release-4.16] Fix 'cross-spawn' CVE #1747

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

DFBUGS-809: [release-4.16] Fix 'cross-spawn' CVE #1747

wants to merge 1 commit into from

Conversation

SanjalKatiyar
Copy link
Collaborator

@SanjalKatiyar SanjalKatiyar commented Nov 29, 2024 •
edited
Loading

@openshift-ci OpenShift CI
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
Copy link
Collaborator Author

SanjalKatiyar commented Nov 29, 2024 •
edited by openshift-ci bot
Loading

/retitle DFBUGS-809: [release-4.16] Fix 'cross-spawn' CVE

@openshift-ci openshift-ci bot changed the title [release-4.16] Cross spawn CVE 416 DFBUGS-809: [release-4.16] Fix 'cross-spawn' CVE Nov 29, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid jira ticket of any type label Nov 29, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 29, 2024 •
edited by openshift-ci bot
Loading

@SanjalKatiyar: This pull request references [Jira Issue DFBUGS-809](https://issues.redhat.com//browse/DFBUGS-809), which is invalid:

  • expected the bug to target the "odf-4.16.4" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

#1695

https://issues.redhat.com/browse/DFBUGS-803
https://issues.redhat.com/browse/DFBUGS-809
https://issues.redhat.com/browse/DFBUGS-815

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/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting label Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
approved jira/invalid-bug Indicates that the referenced jira bug is invalid 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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@SanjalKatiyar @openshift-ci-robot