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

Update dependency org.pitest:pitest-maven to v1.14.2 - autoclosed #703

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 16, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
org.pitest:pitest-maven (source) 1.13.1 -> 1.14.2 age adoption passing confidence

Release Notes

hcoles/pitest

v1.14.2

Compare Source

#​1221 - Unified percentage calculate (thanks @​Vampire)
#​1218 - Thread safety for results collection when tests run in parallel (thanks @​Vampire)
#​1225 - Prevent error when non archive files included on classpath
#​1229 - Mutate Iterables to emptyList
#​1227/1232 - Fix MethodMutator interface to depend on abstract types

v1.14.1

Compare Source

  • #​1215 Apply coverage rewrites when aggregating reports
  • #​1219 Ensure try with resources filtering applied first (thanks @​Vampire)

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


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/pitest.version branch 2 times, most recently from b86b188 to 1c5832f Compare May 19, 2023 15:41
@renovate renovate bot changed the title Update dependency org.pitest:pitest-maven to v1.13.2 Update dependency org.pitest:pitest-maven to v1.14.0 May 19, 2023
@renovate renovate bot force-pushed the renovate/pitest.version branch from 1c5832f to 73cca2b Compare May 25, 2023 12:45
@renovate renovate bot changed the title Update dependency org.pitest:pitest-maven to v1.14.0 Update dependency org.pitest:pitest-maven to v1.14.1 May 25, 2023
@renovate renovate bot force-pushed the renovate/pitest.version branch from 73cca2b to c8dba38 Compare June 10, 2023 14:56
@renovate renovate bot changed the title Update dependency org.pitest:pitest-maven to v1.14.1 Update dependency org.pitest:pitest-maven to v1.14.2 Jun 23, 2023
@renovate renovate bot force-pushed the renovate/pitest.version branch from c8dba38 to a391c10 Compare June 23, 2023 10:10
@renovate renovate bot changed the title Update dependency org.pitest:pitest-maven to v1.14.2 Update dependency org.pitest:pitest-maven to v1.14.2 - autoclosed Jul 14, 2023
@renovate renovate bot closed this Jul 14, 2023
@renovate renovate bot deleted the renovate/pitest.version branch July 14, 2023 20:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants