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

Bug 2091213: Update gopkg.in/yaml.v3 to v3.0.0 for security fix #130

Merged
merged 1 commit into from
Aug 3, 2022

Conversation

jzding
Copy link
Member

@jzding jzding commented Jul 29, 2022

Updates gopkg.in/yaml.v3 to v3.0.0 to fix GHSA-hp87-p4gw-j4gq.
Refer to go-yaml/yaml#666.

Signed-off-by: Jack Ding jacding@redhat.com

Signed-off-by: Jack Ding <jacding@redhat.com>
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 29, 2022

@jzding: This pull request references Bugzilla bug 2091213, which is invalid:

  • expected the bug to target the "4.10.z" release, but it targets "4.10.0" instead
  • expected Bugzilla bug 2091213 to depend on a bug targeting a release in 4.11.0 and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

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

In response to this:

Bug 2091213: Update gopkg.in/yaml.v3 to v3.0.0 for security fix

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/test-infra repository.

@jzding
Copy link
Member Author

jzding commented Jul 29, 2022

/bugzilla refresh

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 29, 2022

@jzding: This pull request references Bugzilla bug 2091213, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.10.z) matches configured target release for branch (4.10.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2091106 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2091106 targets the "4.11.0" release, which is one of the valid target releases: 4.11.0
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (yliu1@redhat.com), skipping review request.

In response to this:

/bugzilla refresh

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/test-infra repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 3, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aneeshkp, jzding

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

@aneeshkp
Copy link
Member

aneeshkp commented Aug 3, 2022

/lgtm

@openshift-ci openshift-ci bot merged commit cc68f85 into redhat-cne:release-4.10 Aug 3, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 3, 2022

@jzding: All pull requests linked via external trackers have merged:

Bugzilla bug 2091213 has been moved to the MODIFIED state.

In response to this:

Bug 2091213: Update gopkg.in/yaml.v3 to v3.0.0 for security fix

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/test-infra repository.

@jzding jzding deleted the gopkg_exception-4.10 branch December 12, 2022 18:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants