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

[3.5] Bump golang-jwt/jwt to 4.5.1 to address GO-2024-3250 #18899

Merged
merged 1 commit into from
Nov 15, 2024

Conversation

tjungblu
Copy link
Contributor

@ivanvc
Copy link
Member

ivanvc commented Nov 15, 2024

/retitle [3.5] Bump golang-jwt/jwt to 4.5.1 to address GO-2024-3250
/retest

@k8s-ci-robot k8s-ci-robot changed the title Bump golang-jwt/jwt to 4.5.1 to address GO-2024-3250 [3.5] Bump golang-jwt/jwt to 4.5.1 to address GO-2024-3250 Nov 15, 2024
Copy link
Member

@ahrtr ahrtr left a comment

Choose a reason for hiding this comment

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

LGTM

Thanks @tjungblu

Copy link
Member

@jmhbnz jmhbnz left a comment

Choose a reason for hiding this comment

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

LGTM - We bumped it in main last week in fed92fa

Thanks @tjungblu

@k8s-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahrtr, jmhbnz, tjungblu

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

@jmhbnz jmhbnz merged commit 5711c07 into etcd-io:release-3.5 Nov 15, 2024
26 checks passed
@ivanvc
Copy link
Member

ivanvc commented Nov 15, 2024

We had a failure in the trivy scan. Again, GHCR replied with a 429 (https://github.com/etcd-io/etcd/actions/runs/11856210750/job/33042258548?pr=18899). Thomas' branch is up to date and has the ECR workaround. It also looks like the error was in another image (not trivy-db). We should keep an eye on this workflow.

ERROR: failed to solve: ghcr.io/aquasecurity/trivy:0.50.1: failed to resolve source metadata for ghcr.io/aquasecurity/trivy:0.50.1: failed to copy: httpReadSeeker: failed open: unexpected status code https://ghcr.io/v2/aquasecurity/trivy/blobs/sha256:17e803800853ecc7564ad672b0d71df4870e4e7586701de79cc40e2ea9819671: 429 Too Many Requests - Server message: toomanyrequests: retry-after: 8.583µs, allowed: 44000/minute

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

5 participants