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

Bump github.com/go-jose/go-jose/v3 from 3.0.1 to 3.0.3 #7750

Merged
merged 1 commit into from
Mar 8, 2024

Conversation

matzew
Copy link
Member

@matzew matzew commented Mar 8, 2024

Fixes #

Proposed Changes

  • Bump github.com/go-jose/go-jose/v3 from 3.0.1 to 3.0.3

Pre-review Checklist

  • At least 80% unit test coverage
  • E2E tests for any new behavior
  • Docs PR for any user-facing impact
  • Spec PR for any new API feature
  • Conformance test for any change to the spec

Release Note

Bump github.com/go-jose/go-jose/v3 from 3.0.1 to 3.0.3

Docs

Signed-off-by: Matthias Wessendorf <mwessend@redhat.com>
@knative-prow knative-prow bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Mar 8, 2024
@dsimansk
Copy link
Contributor

dsimansk commented Mar 8, 2024

/approve
/lgtm

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Mar 8, 2024
Copy link

knative-prow bot commented Mar 8, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dsimansk, matzew

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

Copy link

codecov bot commented Mar 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.15%. Comparing base (f81f1d3) to head (61e551a).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7750   +/-   ##
=======================================
  Coverage   69.15%   69.15%           
=======================================
  Files         339      339           
  Lines       19429    19429           
=======================================
  Hits        13437    13437           
  Misses       5330     5330           
  Partials      662      662           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@knative-prow knative-prow bot merged commit 6f944bf into knative:main Mar 8, 2024
34 of 39 checks passed
@matzew
Copy link
Member Author

matzew commented Mar 12, 2024

/cherry-pick release-1.13

@matzew
Copy link
Member Author

matzew commented Mar 12, 2024

/cherry-pick release-1.12

@knative-prow-robot
Copy link
Contributor

@matzew: #7750 failed to apply on top of branch "release-1.13":

Applying: dizzy: Bump just go-jose to latest
Using index info to reconstruct a base tree...
M	go.mod
M	go.sum
M	vendor/modules.txt
Falling back to patching base and 3-way merge...
Auto-merging vendor/modules.txt
Removing vendor/github.com/go-jose/go-jose/v3/BUG-BOUNTY.md
Auto-merging go.sum
CONFLICT (content): Merge conflict in go.sum
Auto-merging go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 dizzy: Bump just go-jose to latest
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-1.13

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.

@knative-prow-robot
Copy link
Contributor

@matzew: #7750 failed to apply on top of branch "release-1.12":

Applying: dizzy: Bump just go-jose to latest
Using index info to reconstruct a base tree...
M	go.mod
M	go.sum
A	vendor/github.com/go-jose/go-jose/v3/CHANGELOG.md
A	vendor/github.com/go-jose/go-jose/v3/jwt/claims.go
A	vendor/github.com/go-jose/go-jose/v3/jwt/doc.go
M	vendor/github.com/go-jose/go-jose/v3/symmetric.go
M	vendor/modules.txt
Falling back to patching base and 3-way merge...
Auto-merging vendor/modules.txt
CONFLICT (content): Merge conflict in vendor/modules.txt
Auto-merging vendor/google.golang.org/grpc/version.go
CONFLICT (content): Merge conflict in vendor/google.golang.org/grpc/version.go
Auto-merging vendor/github.com/go-jose/go-jose/v3/symmetric.go
CONFLICT (modify/delete): vendor/github.com/go-jose/go-jose/v3/jwt/claims.go deleted in HEAD and modified in dizzy: Bump just go-jose to latest. Version dizzy: Bump just go-jose to latest of vendor/github.com/go-jose/go-jose/v3/jwt/claims.go left in tree.
CONFLICT (modify/delete): vendor/github.com/go-jose/go-jose/v3/CHANGELOG.md deleted in HEAD and modified in dizzy: Bump just go-jose to latest. Version dizzy: Bump just go-jose to latest of vendor/github.com/go-jose/go-jose/v3/CHANGELOG.md left in tree.
Removing vendor/github.com/go-jose/go-jose/v3/BUG-BOUNTY.md
Auto-merging go.sum
CONFLICT (content): Merge conflict in go.sum
Auto-merging go.mod
CONFLICT (content): Merge conflict in go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 dizzy: Bump just go-jose to latest
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-1.12

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants