Skip to content
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

Update sbt-scoverage to 1.9.0 #226

Merged
merged 2 commits into from
Sep 28, 2021
Merged

Update sbt-scoverage to 1.9.0 #226

merged 2 commits into from
Sep 28, 2021

Conversation

47erbot
Copy link
Contributor

@47erbot 47erbot commented Sep 17, 2021

Updates org.scoverage:sbt-scoverage from 1.8.2 to 1.9.0.
GitHub Release Notes - Version Diff

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

Files still referring to the old version number

The following files still refer to the old version number (1.8.2).
You might want to review and update them manually.

CHANGELOG.md
Ignore future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "org.scoverage", artifactId = "sbt-scoverage" } ]

labels: sbt-plugin-update, semver-minor, old-version-remains

@SethTisue
Copy link

The CI failure looks intermittent and unrelated to the change?

It would be convenient for me in the Scala community build if this were merged. And for you, it would pave the way for an eventual upgrade to sbt 1.6.

@47erbot 47erbot merged commit ea5915a into main Sep 28, 2021
@47erbot 47erbot deleted the update/sbt-scoverage-1.9.0 branch September 28, 2021 20:52
@SethTisue
Copy link

thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants