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

chore(deps): update dependency org.pitest:pitest-maven to v1.16.1 #31

Merged
merged 1 commit into from
Jun 14, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 14, 2023

Mend Renovate

This PR contains the following updates:

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

Release Notes

hcoles/pitest (org.pitest:pitest-maven)

v1.16.1

Compare Source

v1.16.0

Compare Source

  • #​1311 - Include unmodifiable collections stored directly to fields in the +funmodifiablecollection filter for defensive code
  • #​1319 - Use environment variables from surefire config
  • #​1322 - Automatically add -ea to enable assertions
  • #​1321 - Expand BuildVerifier interface

Api change in #​1321 is backwards compatible, but plugins written against 1.16.0 may not work with earlier versions.

v1.15.8

Compare Source

#​1310 Filter mutations to Collections.unmodifiable*
#​1309 Replace fields in argLines imported from surefire config
#​1308 Bump maven vcs versions

The filtering for #​1310 is off by default. To activate it add the filter string +funmodifiablecollection.

#​1309 adds a new maven property parseSurefireArgLine. This is set to true by default, but surefire argline parsing can now be disabled by setting it to false.

v1.15.7

Compare Source

#​1305 Coverage not recorded for code in packages name com.sun*

A filter intended to pickup legacy JDK classes in the "com.sun.*" package was missing a ', resulting in no code coverage being registered if the code under test happened to be in a package starting with "sun".

v1.15.6

Compare Source

  • #​1295 temporarily remove dynamic call tracking

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

  • #​1292 Args lines taken from surefire config do not have properties replaced

v1.15.4

Compare Source

  • #​1288 - New extension point to allow custom coverage export formats
  • #​1289 - Parse argline configuration from surefire configuration
  • #​1274 Follow invoke dynamic calls when detecting static initializer only methods

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.

v1.15.3

Compare Source

  • #​1271 - Double check thread status before marking minion as dead

v1.15.2

Compare Source

  • #​1268 - Filter Lombok NonNull checks
  • #​1267 - Expand test api to allow reporting of errors during test scanning

#​1267 will ensure that previously hidden errors encountered by the JUnit5 plugin will now be reported. This is a backwards compatible api change. It will have no effect until the JUnit5 plugin is updated to use the expanded api. The updated plugin will not be compatible with earlier versions of pitest.

v1.15.1

Compare Source

  • #​1260 Upgrade to ASM 9.6 for Java 22 support
  • #​1261 Do not error on pitest history files < 1.15.0

v1.15.0

Compare Source

  • #​1253 suppress coverage stats when history test reduction enabled
  • #​1252 add extrafeatures param for maven to allow features to be added on commandline without overwriting existing list
  • #​1251 expand history interfaces (breaking change)
  • #​1250 improve error message when failing to parse feature strings
  • #​1248 performance tweak - delay test class identification
  • #​1247 legacy code removal

#​1251 updates several existing interfaces. Plugins (eg the arcmutate kotlin plugin) using these interfaces must also be updated when upgrading.

v1.14.4

Compare Source

  • #​1246 Priotitise previous killing test when using history files

v1.14.3

Compare Source

  • #​1239 Support comma seperated excludedGroups (thanks @​johnathana)
  • #​1243 Explictly order classpath in history file to ensure consitency between runs
  • #​1245 Prevent confusing logging of dummy incremental analysis runs

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

v1.13.1

Compare Source

v1.13.0

Compare Source

  • #​1188 Allow mutators to produce multiple distinct mutations
  • #​1190 Provide test prioritiser to interceptors
  • #​1191 Enable mutation of annotations of methods and fields

v1.12.0

Compare Source

Adds new extension points to allow plugins to make changes in the environment in which tests are run.


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 changed the title Update dependency org.pitest:pitest-maven to v1.15.3 chore(deps): update dependency org.pitest:pitest-maven to v1.15.3 Dec 20, 2023
@renovate renovate bot force-pushed the renovate/pitest.version branch 2 times, most recently from 286e23e to 595454f Compare December 22, 2023 09:52
@renovate renovate bot force-pushed the renovate/pitest.version branch from 595454f to 318bcb2 Compare January 20, 2024 05:44
@renovate renovate bot changed the title chore(deps): update dependency org.pitest:pitest-maven to v1.15.3 chore(deps): update dependency org.pitest:pitest-maven to v1.15.4 Jan 20, 2024
@renovate renovate bot changed the title chore(deps): update dependency org.pitest:pitest-maven to v1.15.4 chore(deps): update dependency org.pitest:pitest-maven to v1.15.6 Jan 24, 2024
@renovate renovate bot force-pushed the renovate/pitest.version branch from 318bcb2 to 4a1cd97 Compare January 24, 2024 11:50
@renovate renovate bot force-pushed the renovate/pitest.version branch from 4a1cd97 to 4795ad4 Compare February 6, 2024 01:54
@renovate renovate bot changed the title chore(deps): update dependency org.pitest:pitest-maven to v1.15.6 chore(deps): update dependency org.pitest:pitest-maven to v1.15.7 Feb 6, 2024
@renovate renovate bot force-pushed the renovate/pitest.version branch from 4795ad4 to f210703 Compare February 14, 2024 13:42
@renovate renovate bot changed the title chore(deps): update dependency org.pitest:pitest-maven to v1.15.7 chore(deps): update dependency org.pitest:pitest-maven to v1.15.8 Feb 14, 2024
@renovate renovate bot force-pushed the renovate/pitest.version branch from f210703 to 664fcb7 Compare March 26, 2024 08:43
@renovate renovate bot force-pushed the renovate/pitest.version branch from 664fcb7 to 157cabc Compare April 10, 2024 00:21
@renovate renovate bot changed the title chore(deps): update dependency org.pitest:pitest-maven to v1.15.8 chore(deps): update dependency org.pitest:pitest-maven to v1.16.0 Apr 10, 2024
@renovate renovate bot changed the title chore(deps): update dependency org.pitest:pitest-maven to v1.16.0 chore(deps): update dependency org.pitest:pitest-maven to v1.16.1 May 9, 2024
@renovate renovate bot force-pushed the renovate/pitest.version branch from 157cabc to a15a963 Compare May 9, 2024 14:56
@renovate renovate bot force-pushed the renovate/pitest.version branch from a15a963 to 31960d3 Compare May 13, 2024 13:05
@marcberger marcberger merged commit d99dfd9 into main Jun 14, 2024
1 check failed
@marcberger marcberger deleted the renovate/pitest.version branch June 14, 2024 08:30
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.

1 participant