Bump pitest-maven from 1.12.0 to 1.13.0

[dependabot]

Bumps pitest-maven from 1.12.0 to 1.13.0.

Release notes

Sourced from pitest-maven's releases.

1.13.0

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

Commits

• 61636b3 release 1.13.0
• c6a4989 Merge pull request #1191 from hcoles/feature/field_mutation2
• 812670a enable annotation mutations
• adc90d4 enable field mutation
• e429fb9 Merge pull request #1190 from hcoles/feature/early_coverage_assignment
• 6e66a47 make test prioritised available to interceptors
• 7d5e20a Merge pull request #1188 from hcoles/feature/multi_mutators
• 2a2b827 Merge pull request #1187 from hcoles/feature/autoset_use_classpath_jar
• 4c36688 use classpath jar when classpath file provided
• 7be0cb7 allow multiple mutations per mutator
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

JUnit test results

  4 005 files  ±0    4 005 suites  ±0   56s ⏱️ +3s
19 404 tests +1  19 360 ✔️ +1  44 💤 ±0  0 ❌ ±0 
19 497 runs  ±0  19 453 ✔️ ±0  44 💤 ±0  0 ❌ ±0 

Results for commit e224801. ± Comparison against base commit 8c51772.

This pull request removes 1210 and adds 1103 tests. Note that renamed tests count towards both.

  

  b
  -1000000000-01-01T00:00:00Z
  07:10
  07:10Z
  07:23
  07:23Z
  2017-03-08T07:10
  2017-03-08T07:10-05:00[America/New_York]
…

AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[1] org.assertj.core.api.InstantAssert@1, org.assertj.core.api.InstantAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@51, 2017-03-12T07:12:00Z, 2017-03-12T07:12:00Z, 2017-03-08T07:10:00Z, 2017-03-08T07:10:00Z, 
Expecting actual:
  2017-03-12T07:10:00Z
to be close to:
  2017-03-08T07:10:00Z
within 50 Hours but difference was 96 Hours, null
AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[2] org.assertj.core.api.InstantAssert@1, org.assertj.core.api.InstantAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@21, 2017-03-12T07:10:00.001Z, 2017-03-12T07:10:00.001Z, -1000000000-01-01T00:00:00Z, -1000000000-01-01T00:00:00Z, 
Expecting actual:
  2017-03-12T07:10:00Z
to be close to:
  -1000000000-01-01T00:00:00Z
within 2 Millis but difference was PT8765837682367H10M, null
AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[3] org.assertj.core.api.LocalDateTimeAssert@1, org.assertj.core.api.LocalDateTimeAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@51, 2017-03-10T07:12, 2017-03-10T07:12:00, 2017-03-08T07:10, 2017-03-08T07:10:00, 
Expecting actual:
  2017-03-12T07:10
to be close to:
  2017-03-08T07:10
within 50 Hours but difference was 96 Hours, null
AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[4] org.assertj.core.api.LocalDateAssert@1, org.assertj.core.api.LocalDateAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@22, 2017-03-10, 2017-03-10, 2017-03-27, 2017-03-27, 
Expecting actual:
  2017-03-12
to be close to:
  2017-03-27
within 3 Days but difference was 15 Days, org.assertj.core.data.TemporalUnitWithinOffset@20
AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[5] org.assertj.core.api.LocalTimeAssert@1, org.assertj.core.api.LocalTimeAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@24, 07:12, 07:12:00, 07:23, 07:23:00, 
Expecting actual:
  07:10
to be close to:
  07:23
within 5 Minutes but difference was 13 Minutes, org.assertj.core.data.TemporalUnitWithinOffset@20
AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[6] org.assertj.core.api.OffsetDateTimeAssert@1, org.assertj.core.api.OffsetDateTimeAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@29, 2017-03-12T07:12Z, 2017-03-12T07:12:00Z, 2017-03-12T07:23Z, 2017-03-12T07:23:00Z, 
Expecting actual:
  2017-03-12T07:10Z
to be close to:
  2017-03-12T07:23Z
within 10 Minutes but difference was 13 Minutes, null
AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[7] org.assertj.core.api.ZonedDateTimeAssert@1, org.assertj.core.api.ZonedDateTimeAssert@1, org.assertj.core.data.TemporalUnitLessThanOffset@7e, 2017-03-10T07:12-05:00[America/New_York], 2017-03-10T07:12:00-05:00[America/New_York], 2017-03-08T07:10-05:00[America/New_York], 2017-03-08T07:10:00-05:00[America/New_York], 
Expecting actual:
  2017-03-12T07:10-04:00[America/New_York]
to be close to:
  2017-03-08T07:10-05:00[America/New_York]
by less than 95 Hours but difference was 95 Hours, null
AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[8] org.assertj.core.api.OffsetTimeAssert@1, org.assertj.core.api.OffsetTimeAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@21, 07:12Z, 07:12:00Z, 07:23Z, 07:23:00Z, 
Expecting actual:
  07:10Z
to be close to:
  07:23Z
within 2 Minutes but difference was 13 Minutes, org.assertj.core.data.TemporalUnitWithinOffset@20
AbstractTemporalAssert isCloseTo ‑ should fail if offset parameter is null (ArgumentsAccessor)[1] org.assertj.core.api.InstantAssert@1, org.assertj.core.api.InstantAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@51, 2017-03-12T07:12:00Z, 2017-03-12T07:12:00Z, 2017-03-08T07:10:00Z, 2017-03-08T07:10:00Z, 
Expecting actual:
  2017-03-12T07:10:00Z
to be close to:
  2017-03-08T07:10:00Z
within 50 Hours but difference was 96 Hours, null
AbstractTemporalAssert isCloseTo ‑ should fail if offset parameter is null (ArgumentsAccessor)[2] org.assertj.core.api.InstantAssert@1, org.assertj.core.api.InstantAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@21, 2017-03-12T07:10:00.001Z, 2017-03-12T07:10:00.001Z, -1000000000-01-01T00:00:00Z, -1000000000-01-01T00:00:00Z, 
Expecting actual:
  2017-03-12T07:10:00Z
to be close to:
  -1000000000-01-01T00:00:00Z
within 2 Millis but difference was PT8765837682367H10M, null
…

♻️ This comment has been updated with latest results.