Skip to content
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

Merged
merged 1 commit into from
May 24, 2023

Conversation

Picnic-Bot
Copy link
Contributor

@Picnic-Bot Picnic-Bot commented May 18, 2023

This PR contains the following updates:

Package Type Update Change
org.pitest:pitest-maven (source) build minor 1.13.1 -> 1.14.0

Release Notes

hcoles/pitest

v1.14.0

Compare Source

  • #​1213 Filter equivalent divide by -1 maths mutants
  • #​1212 Auto add junit-platform-launcher

#​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


  • If you want to rebase/retry this PR, check this box

@Picnic-Bot
Copy link
Contributor Author

Picnic-Bot commented May 18, 2023

Suggested commit message:

Upgrade pitest-maven-plugin 1.13.1 -> 1.14.0 (#633)

See:
- https://github.com/hcoles/pitest/releases/tag/1.13.2
- https://github.com/hcoles/pitest/releases/tag/1.14.0
- https://github.com/hcoles/pitest/compare/1.13.1...1.14.0

@Stephan202 Stephan202 added this to the 0.12.0 milestone May 18, 2023
Copy link
Member

@Stephan202 Stephan202 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Output is unchanged.

@Picnic-Bot Picnic-Bot force-pushed the renovate/org.pitest-pitest-maven-1.x branch from 9105d63 to 9c9d8f5 Compare May 20, 2023 01:01
@Picnic-Bot Picnic-Bot changed the title Upgrade org.pitest:pitest-maven 1.13.1 -> 1.13.2 Upgrade org.pitest:pitest-maven 1.13.1 -> 1.14.0 May 20, 2023
@Stephan202
Copy link
Member

Version 1.14.0 also LGTM.

@Picnic-Bot Picnic-Bot force-pushed the renovate/org.pitest-pitest-maven-1.x branch 2 times, most recently from cbb2e70 to 79663c6 Compare May 24, 2023 01:01
@rickie rickie force-pushed the renovate/org.pitest-pitest-maven-1.x branch from 79663c6 to d54d057 Compare May 24, 2023 14:11
@github-actions
Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@rickie rickie merged commit d0bbc5c into master May 24, 2023
@rickie rickie deleted the renovate/org.pitest-pitest-maven-1.x branch May 24, 2023 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants