-
Notifications
You must be signed in to change notification settings - Fork 91
CVE-2025-30204: update golang-jwt #1249
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
CVE-2025-30204: update golang-jwt #1249
Conversation
|
Hi @artem-panchenko , thanks for your contribution! Would you mind sign off your git commit? See the details at https://github.com/notaryproject/notation/pull/1249/checks?check_run_id=39909230540. We will discuss about the release of a security patch in the next community meeting. If you have any questions, feel free to join the slack channel to connect with the community. |
8096a5e to
9692326
Compare
ghost
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## release-1.3 #1249 +/- ##
============================================
Coverage 70.65% 70.65%
============================================
Files 48 48
Lines 2944 2944
============================================
Hits 2080 2080
Misses 671 671
Partials 193 193 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
JeyJeyGao
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
Hi @artem-panchenko , the merge is blocked due to a missing commit signature. Could you please sign your commit? Thanks! |
9692326 to
24e424b
Compare
Signed-off-by: Artem Panchenko <artem.panchenko@datarobot.com>
24e424b to
d8636f3
Compare
|
@JeyJeyGao Done. Thanks! |
Please consider merging this small security patch and then issue a new 1.3.2 release if the
release-1.3branch is still maintained. Thanks!