-
Notifications
You must be signed in to change notification settings - Fork 39
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 org.pitest:pitest-maven 1.13.1 -> 1.14.0 #633
Conversation
Suggested commit message:
|
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.
Output is unchanged.
9105d63
to
9c9d8f5
Compare
Version 1.14.0 also LGTM. |
cbb2e70
to
79663c6
Compare
79663c6
to
d54d057
Compare
Looks good. No mutations were possible for these changes. |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
This PR contains the following updates:
1.13.1
->1.14.0
Release Notes
hcoles/pitest
v1.14.0
Compare Source
#1212 Largely resolves the issue of keeping the pitest-junit5-plugin version in sync with the junit5 version for maven users.
When used with 1.2.0 of the pitest-junit5-plugin, pitest will now automatically select a version of junit-platform-launcher which is compatible with the version of junit5 used by the system under test.
Issues remain for gradle users who may still encounter api compatibilities when using 1.2.0 of the pitest-junit5-plugin. These can however now be resolved by manually adding the correct version of junit-platform-launcher to the classpath.
It is hoped that a future version of the pitest gradle plugin will implement a fix similar to the pitest-maven solution.
v1.13.2
Compare Source