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
Upgrade byte buddy to 1.10.5 #1842
Conversation
11a6e92
to
38bee9a
Compare
Codecov Report
@@ Coverage Diff @@
## release/3.x #1842 +/- ##
==============================================
Coverage 86.64% 86.64%
Complexity 2507 2507
==============================================
Files 314 314
Lines 6613 6613
Branches 829 829
==============================================
Hits 5730 5730
Misses 682 682
Partials 201 201 Continue to review full report at Codecov.
|
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.
Thanks!
@TimvdLippe any chance of releasing this? |
@villesau This has been released on Bintray: https://bintray.com/mockito/maven/mockito-development/3.1.13 |
@TimvdLippe looks like it's still not visible in github releases: https://github.com/mockito/mockito/releases |
Yeah Mockito 3.2.1 was incorrectly tagged. Fixed in 4c29061 |
Great, thanks for the help @TimvdLippe! :) |
@TimvdLippe one question still: Why it's not released in maven yet? https://mvnrepository.com/artifact/org.mockito/mockito-core/3.2.0 Not a biggie, just wondering. |
@villesau please see the explanation in the README: https://github.com/mockito/mockito/blob/release/3.x/README.md#how-to-release-new-version |
check list
including project members to get a better picture of the change
commit is meaningful and help the people that will explore a change in 2 years
Fixes #<issue number>
in the description if relevantFixes #<issue number>
if relevantFixes #1841
Byte buddy had a bug that prevented running tests in IntelliJ that's now fixed.