-
Notifications
You must be signed in to change notification settings - Fork 4
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.scoverage:sbt-scoverage to v1.9.3 - abandoned #42
base: master
Are you sure you want to change the base?
Conversation
9e6f2f7
to
1f506d9
Compare
1f506d9
to
10e8fcd
Compare
10e8fcd
to
3c5706d
Compare
3c5706d
to
7b333ff
Compare
7b333ff
to
b82c0fc
Compare
b82c0fc
to
5ee2224
Compare
5ee2224
to
6072e6f
Compare
6072e6f
to
bccd965
Compare
bccd965
to
d329652
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
Autoclosing SkippedThis PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error. |
This PR contains the following updates:
1.6.1
->1.9.3
Release Notes
scoverage/sbt-scoverage
v1.9.3
Compare Source
What’s Changed
v1.9.2
Compare Source
What’s Changed
v1.9.1
Compare Source
What’s Changed
v1.9.0
Compare Source
What’s Changed
v1.8.2
: sbt-scoverage v1.8.2Compare Source
What’s Changed
v1.8.1
: sbt-scoverage v1.8.1Compare Source
What’s Changed
v1.8.0
: sbt-scoverage v1.8.0Compare Source
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 likethe following:
Then you'd run your tests, and the output would be as follows:
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 thestatement 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 ofcoverageMinimumStmtTotal
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:
New Features
Bug Fixes
Housekeeping
Big thanks to everyone that made this release possible!
v1.7.3
Compare Source
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
Compare Source
What’s Changed
v1.7.1
: sbt-scoverage v1.7.1Compare Source
Small release adding support for the latest scoverage 1.4.4
v1.7.0
: sbt-scoverage v1.7.0Compare Source
coverageCleanSubprojectFiles
key has been removedConfiguration
📅 Schedule: Branch creation - "every weekend" (UTC), 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.
This PR has been generated by Mend Renovate. View repository job log here.