Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork158
Updateextract to 4.0.0 and golang to 1.23#990
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
codecov-commenter commentedAug 29, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@## main #990 +/- ##======================================= Coverage 20.85% 20.85% ======================================= Files 42 42 Lines 2570 2570 ======================================= Hits 536 536 Misses 1949 1949 Partials 85 85
Flags with carried forward coverage won't be shown.Click here to find out more. ☔ View full report in Codecov by Sentry. |
alessio-perugini 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. Why not upgrade directly to go 1.23? 🤔
cmaglie commentedAug 29, 2024
Yes, why... I've updated to 1.23 :-) |
extract to 4.0.0 and golang to 1.22extract to 4.0.0 and golang to 1.23
Uh oh!
There was an error while loading.Please reload this page.
Please check if the PR fulfills these requirements
before creating one)
What kind of change does this PR introduce?
Updates:
extractto version 4.0.0What is the current behavior?
What is the new behavior?
Does this PR introduce a breaking change?
Other information: