search

MikeSafonov / jira-telegram-bot

Telegram bot for notifications about Jira events
MIT License
14 stars 6 forks source link

build(deps): bump gradle-pitest-plugin from 1.4.0 to 1.9.11 #145

Open dependabot[bot] opened 1 year ago

dependabot[bot] commented 1 year ago

Bumps gradle-pitest-plugin from 1.4.0 to 1.9.11.

Release notes

Sourced from gradle-pitest-plugin's releases.

1.9.11

  • Support for thresholds in aggregated metrics (requires PIT 1.9.9+) - #319 - PR by pfoerd
  • Support for verbosity flag, "spinner" disabled by default - #267 - PR by Carsten Otto
  • PIT 1.9.11 by default
  • Do not produce timestamped reports by default for PIT 1.9.6+ - suggestion by Siddardha Bezawada
  • Minimal supported PIT version is 1.7.1 (due to "verbosity" flag used by default)
  • Deprecate verbose flag - verbosity is much more versatile, especially when used from the Gradle plugin

Compatibility notes

  1. Due to the usage of the "verbosity" flag by default, the minimal supported PIT version is 1.7.1 (released 2021-09-29).
  2. Due to the changes in PIT 1.9.6, timestamped reported are not generated by default (with PIT 1.9.6+). It still can be enforced in the GPP configuration.

1.9.0

  • PIT 1.9.4 by default (requires pitest-junit5-plugin 1.0.0!)
  • Deprecate support for JDK 8 - #299
  • Support for inputEncoding and outputEncoding (named in plugin inputCharset and outputCharset) - #310
  • Add pitest dependencies only during configuration resolution - #313 - PR by Ian O'Malley
  • Improve build cache hit cache with relative path - #315 - PR by Siddardha Bezawada
  • Remove (optional) dependencyDistance configuration parameter removed in PIT 1.9.0 - #311

Compatibility notes

  1. Due to the plugin API changes in PIT 1.9.0, the new pitest-junit5-plugin 1.0.0 is required (other PIT plugins - if used - also need to be upgraded).
  2. The plugin is released with JDK 11. Source/class compatibility is still set to JDK 8, but this might change without notice.

1.7.4

  • Do not pass --testPlugin for PIT 1.6.7+ for forward compatibility - #277
  • Deprecate testPlugin configuration parameter (not needed in PIT 1.6.7+, to be removed in PIT 1.8.0) - #277
  • PIT 1.7.4 by default
  • Upgrade Gradle wrapper to 6.9.2
  • Test for exclusion of certain mutators - #303 - PR by Narendra Pathai

Compatibility notes:

  1. The testPlugin configuration parameter is deprecated and should not be used. In fact, starting with 1.6.7 it is no longer used (it is enough to add the PIT plugin as a buildscript dependency or just set junit5PluginVersion to use the JUnit 5 plugin). In addition, that property is planned to be removed in PIT 1.8.0.
  2. Using junit5PluginVersion no longer internally set testPlugin property. For using with old PIT (<1.6.7) it is required to set it explicitly in configuration.

1.7.0

  • Support for Gradle configuration cache - #249 - PR by David Burstrom
  • Turn on cacheability for PitestTask - #67 - PR by David Burstrom
  • PIT 1.7.0 by default
  • Fix deprecation warnings in Gradle 7 - #283 - PR by Mike Duigou
  • Bump minimal supported Gradle version to 6.4 - required to fix deprecation warnings in Gradle 7
  • Remove unused maxMutationsPerClass configuration parameter - #266
  • Regression tests for JUnit Jupiter 5.8 (with JUnit Platform 1.8) and pitest-junit5-plugin 0.15
  • Upgrade Gradle wrapper to 6.9.1
  • Switch CI from defunct travis-ci.org to travis-ci.com

Compatibility notes:

  1. Gradle 6.4+ is required (to fix deprecation warnings in Gradle 7)
  2. Not directly related with this plugin, but keep in mind that JUnit Jupiter 5.8 (JUnit Platform 1.8) requires pitest-junit5-plugin 0.15+, while 5.7 (1.7) requires <=0.14. Set right plugin version for JUnit 5 version used in your project to avoid runtime errors (such as NoSuchMethodError: 'java.util.Optional org.junit.platform.commons.util.AnnotationUtils.findAnnotation(java.lang.Class, java.lang.Class, boolean)' - see #300).

... (truncated)

Changelog

Sourced from gradle-pitest-plugin's changelog.

1.9.11 - 2022-11-27

  • Support for thresholds in aggregated metrics (requires PIT 1.9.9+) - #319 - PR by pfoerd
  • Support for verbosity flag, "spinner" disabled by default - #267 - PR by Carsten Otto
  • PIT 1.9.11 by default
  • Do not produce timestamped reports by default for PIT 1.9.6+ - suggestion by Siddardha Bezawada
  • Minimal supported PIT version is 1.7.1 (due to "verbosity" flag used by default)
  • Deprecate verbose flag - verbosity is much more versatile, especially when used from the Gradle plugin

Compatibility notes

  1. Due to the usage of the "verbosity" flag by default, the minimal supported PIT version is 1.7.1 (released 2021-09-29).
  2. Due to the changes in PIT 1.9.6, timestamped reported are not generated by default (with PIT 1.9.6+). It still can be enforced in the GPP configuration.

1.9.0 - 2022-08-19

  • PIT 1.9.4 by default (requires pitest-junit5-plugin 1.0.0!)
  • Deprecate support for JDK 8 - #299
  • Support for inputEncoding and outputEncoding (named in plugin inputCharset and outputCharset) - #310
  • Add pitest dependencies only during configuration resolution - #313 - PR by Ian O'Malley
  • Improve build cache hit cache with relative path - #315 - PR by Siddardha Bezawada
  • Remove (optional) dependencyDistance configuration parameter removed in PIT 1.9.0 - #311

Compatibility notes

  1. Due to the plugin API changes in PIT 1.9.0, the new pitest-junit5-plugin 1.0.0 is required (other PIT plugins - if used - also need to be upgraded).
  2. The plugin is released with JDK 11. Source/class compatibility is still set to JDK 8, but this might change without notice.

1.7.4 - 2022-03-12

  • Do not pass --testPlugin for PIT 1.6.7+ for forward compatibility - #277
  • Deprecate testPlugin configuration parameter (not needed in PIT 1.6.7+, to be removed in PIT 1.8.0) - #277
  • PIT 1.7.4 by default
  • Upgrade Gradle wrapper to 6.9.2
  • Test for exclusion of certain mutators - #303 - PR by Narendra Pathai

Compatibility notes:

  1. The testPlugin configuration parameter is deprecated and should not be used. In fact, starting with 1.6.7 it is no longer used (it is enough to add the PIT plugin as a buildscript dependency or just set junit5PluginVersion to use the JUnit 5 plugin). In addition, that property is planned to be removed in PIT 1.8.0.
  2. Using junit5PluginVersion no longer internally set testPlugin property. For using with old PIT (<1.6.7) it is required to set it explicitly in configuration.

1.7.0 - 2021-09-20

  • Support for Gradle configuration cache - #249 - PR by David Burstrom
  • Turn on cacheability for PitestTask - #67 - PR by David Burstrom
  • PIT 1.7.0 by default
  • Fix deprecation warnings in Gradle 7 - #283 - PR by Mike Duigou
  • Bump minimal supported Gradle version to 6.4 - required to fix deprecation warnings in Gradle 7
  • Remove unused maxMutationsPerClass configuration parameter - #266

... (truncated)

Commits


Dependabot compatibility score

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)