Bump spock-reports from 1.8.0 to 2.0-groovy-3.0

[dependabot-preview]

Bumps spock-reports from 1.8.0 to 2.0-groovy-3.0.

Changelog

Sourced from spock-reports's changelog.

News

Most recent first

• 18th of May 2021

Spock 2.0 has been released!!! This spock-reports release has no functional changes, it just upgrades to Spock 2.0-groovy-3.0.

• 03rd of May 2021

Another minor release to keep up with Spock release candidates: spock-reports 2.0-RC4 is compatible with Spock 2.0-M5-groovy-3.0.

This release does fix one minor issue, #212, which could cause a spock-reports Exception when a Spec failed in a certain way due to a previous update to keep up with Spock in which a constructor call for a constructor that has changed was missed.

It also improves the computation of errors and failures counts, as well as success rate.

• 13th of February 2021

Minor release to fix the POM published in the previous version, which was incorrect due to a careless change to use the new, recommended BOM feature from Gradle!

This release also marks the first release where spock-reports is published only to Maven Central, dropping JCenter releases. This is due to the recent announcement by Bintray that JCenter will be shutdown in April 2021, unfortunately.

Make sure you change all your projects to use Maven Central instead of JCenter.

• 05th of January 2021

A lot of folks seem to be interested in migrating to Spock 2.x even before it stabilizes! So I decided to listen to them and merge all fixes from the 1.8.0 branch into master, and release a new spock-reports version that now uses Spock version 2.0-M4-groovy-3.0. Thankfully, Spock has not changed much since the last milestone, so this upgrade should go smoothly for everyone, including spock-reports itself.

For now, the Spcok reports will include additional information on the feature title when a feature contains examples and is not unrolled... this is a useful feature if you don't use spock-reports, but as spock-reports has always shown the examples even in such cases, this is not really helpful in spock-reports, so I intend to remove that at a future release, before 2.0. For now, though, this release should let you enjoy the newest, shiny Spock version.

TL;DR if you want to use the latest Spock 2/Groovy 3, upgrade to spock-reports version 2.0-RC3 and have fun.

• 04th of October 2020

Released spock-reports version 1.8.0 adding more statistics to reports (see issue #193) and to fix Java 9+ support when using JPMS modules (thanks to @​fenixcitizen for the contribution).

... (truncated)

Commits

• See full diff 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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)