-
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 pitest-maven-plugin 1.15.3 -> 1.15.6 #984
Conversation
Suggested commit message:
|
Looks good. No mutations were possible for these changes. |
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.
This version generates fewer mutations, so I propose that we don't upgrade. I filed hcoles/pitest#1291.
Separately from that we should review to what extent this comment should be tweaked.
6ffd3a4
to
2da05da
Compare
Looks good. No mutations were possible for these changes. |
2da05da
to
63e5929
Compare
Looks good. No mutations were possible for these changes. |
1 similar comment
Looks good. No mutations were possible for these changes. |
63e5929
to
5809b22
Compare
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 now as before 👍
9930a97
to
21cc19c
Compare
Looks good. No mutations were possible for these changes. |
21cc19c
to
af79c53
Compare
Looks good. No mutations were possible for these changes. |
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
This PR contains the following updates:
1.15.3
->1.15.6
Release Notes
hcoles/pitest (pitest-maven-plugin)
v1.15.6
Compare Source
Invoke dynamic call tracking for static initializer code will be reintroduced when additional logic to suppress mutation filtering for delayed execution code has been implemented.
v1.15.5
Compare Source
v1.15.4
Compare Source
Note, maven users who have previously needed to duplicate argline parameters between surefire and pitest's jvmArgs and argline parameters may need to adjust their configuration when upgrading. Entries supplied to surefire will now automatically be added to pitest.