slick-jdbc-extension-scala
slick-jdbc-extension-scala copied to clipboard
Update dependency org.scoverage:sbt-scoverage to v2
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| org.scoverage:sbt-scoverage (source) | plugin | major | 1.6.0 -> 2.0.6 |
Release Notes
scoverage/sbt-scoverage
v2.0.6
What’s Changed
- Allow sbt-scoverage to work on windows (#465) @stevedlawrence
v2.0.5
What’s Changed
v2.0.4
What’s Changed
v2.0.3
What’s Changed
- dep: bump scoverage version to 2.0.3 (#460) @ckipp01
- Fix typo on Scala version check (#457) @JD557
- Update scalafmt-core to 3.5.9 (#455) @scala-steward
v2.0.2
What’s Changed
- dep: bump scoverage version to 2.0.2 (#453) @ckipp01
- chore: make it clearer that the user should update to 3.2.x (#452) @ckipp01
- Add sbt-vspp for publishing the SBT plug-in in a Maven-consistent format (#449) @ScalaWilliam
v2.0.1
What’s Changed
- dep: bump scoverage version to 2.0.1 (#447) @ckipp01
- Update sbt, scripted-plugin to 1.7.1 (#446) @scala-steward
- Refresh excluding packages and files (#443) @rolandtritsch
- Update scalafmt-core to 3.5.8 (#442) @scala-steward
v2.0.0
Please see the previous RC and Milestone releases for any information on breaking changes. This finally releases v2.0.0 of sbt-scoverage which most notably uses scoverage 2.0.0 offering support for Scala 3 starting with the 3.2.x series. Thanks to all the contributors both on the scoverage side and on the dotc side!
What’s Changed
v1.9.3
What’s Changed
- dep: bump default scoverage version to 1.4.11 (#413) @ckipp01
- dep: bump scalafmt to 3.3.1 (#412) @ckipp01
- dep: bump sbt to 1.6.1 (#411) @ckipp01
- Update sbt-scalafmt to 2.4.6 (#408) @scala-steward
- Update Scalafmt to 3.1.2 (#398) @exoego
- Update sbt, scripted-plugin to 1.5.8 (#406) @scala-steward
- Update sbt, scripted-plugin to 1.5.7 (#404) @scala-steward
v1.9.2
What’s Changed
v1.9.1
What’s Changed
- Ensure reporting and aggregation still works when disabling modules. (#377) @ckipp01
- Update scalafmt-core to 3.0.6 (#375) @scala-steward
- Update sbt-ci-release to 1.5.9 (#373) @scala-steward
- Update scalafmt-core to 3.0.4 (#371) @scala-steward
v1.9.0
What’s Changed
- Update default scoverage to 1.4.9 (#370) @ckipp01
- provide possibility to set up data dir(Rebased to newest version) (#366) @pzhong-livongo
- Update scalafmt-core to 3.0.3 (#367) @scala-steward
- Update scalafmt-core to 3.0.2 (#365) @scala-steward
- Update scalafmt-core to 3.0.1 (#364) @scala-steward
- Update scalafmt-core to 3.0.0 (#363) @scala-steward
- Update sbt, scripted-plugin to 1.5.5 (#361) @scala-steward
- Update sbt-scalafmt to 2.4.3 (#359) @scala-steward
- Update sbt, scripted-plugin to 1.5.4 (#357) @scala-steward
- Update to scala 2.12.14 (#356) @samupra
- Update sbt, scripted-plugin to 1.5.3 (#355) @scala-steward
v1.8.2: sbt-scoverage v1.8.2
What’s Changed
- Update scalac-scoverage-plugin to 1.4.8 (#354) @scala-steward
v1.8.1: sbt-scoverage v1.8.1
What’s Changed
- Bump scoverage version to 1.4.7 (#353) @ckipp01
- Add in .git-blame-ignore-revs (#351) @ckipp01
- Add in missing percent sign for branch coverage (#350) @ckipp01
v1.8.0: sbt-scoverage v1.8.0
The v1.8.0 release is the first release in a while to bring some new features!
One thing you may have noticed in the past was some confusion around how
coverageMinimum was calculated. For example you would often see something like
the following:
// build.sbt
coverageMinimum := 80
Then you'd run your tests, and the output would be as follows:
[info] Statement coverage.: 81.00%
[info] Branch coverage....: 70.00%
[info] Coverage reports completed
[info] All done. Coverage was [81.00%]
You may be wondering how does that equate to 81%? There has been quite a few
issues reported in the past that referred to the average not being correct.
However, the coverageMinimum is not an actual average, but simply the
statement coverage. So while branch coverage is shown, it has no effect on the
actual percentage used to fail your build or to show you your end coverage
percentage. This is part of the reason why we've decided to deprecate
coverageMinimum in favor of coverageMinimumStmtTotal to make this clearer.
Another reason is due to the newly added more fine-grained controls you have for coverage totals thanks to the great work by @kitbellew. Now we are able to have much finer control over the various totals with the introduction of some new setting keys that can all be used to fail your build:
coverageMinimumStmtTotal := 90
coverageMinimumBranchTotal := 90
coverageMinimumStmtPerPackage := 90
coverageMinimumBranchPerPackage := 85
coverageMinimumStmtPerFile := 85
coverageMinimumBranchPerFile := 80
New Features
- Coverage minima: add more fine-grained control (#253) @kitbellew
- Report test names (#297) @vincentdehaan
- Added TeamCity branch coverage reporting (#258) @alexnikitchuk
Bug Fixes
Housekeeping
- Bump scoverage version to 1.4.6 (#349) @ckipp01
- Update sbt, scripted-plugin to 1.5.2 (#348) @scala-steward
- Update tests in scripted. (#347) @ckipp01
- Overhaul the README (#346) @ckipp01
- Add in Scalafmt (#344) @ckipp01
- Remove local snapshot version (#343) @ckipp01
Big thanks to everyone that made this release possible!
v1.7.3
What’s Changed
While we normally wouldn't publish a release just for this, but this could potentially cause issues with clashing classpaths if the BuildInfo wasn't namespaced.
v1.7.2
What’s Changed
- Update to latest scoverage 1.4.5 (#341) @ckipp01
- Test on jdk 8 and 11 (#340) @ckipp01
- Add in dependabot for actions, and release drafter stuff. (#338) @ckipp01
- Update default branch from master to main (#337) @ckipp01
v1.7.1: sbt-scoverage v1.7.1
Small release adding support for the latest scoverage 1.4.4
v1.7.0: sbt-scoverage v1.7.0
coverageCleanSubprojectFileskey has been removed- No longer cross sbt published. sbt 1.2.8 is now required
- Only support for Scala 2.12+ versions.
v1.6.1
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.