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 scalatest to 3.2.19 #319

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

scala-steward
Copy link
Contributor

@scala-steward scala-steward commented Jun 24, 2024

About this PR

πŸ“¦ Updates org.scalatest:scalatest from 3.0.9 to 3.2.19

πŸ“œ GitHub Release Notes - Version Diff

Usage

βœ… Please merge!

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!

πŸ’‘ Applied Scalafix Migrations
πŸ” Files still referring to the old version number

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

build.sbt
βš™ Adjust future updates

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

updates.ignore = [ { groupId = "org.scalatest", artifactId = "scalatest" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalatest", artifactId = "scalatest" }
}]
labels: test-library-update, early-semver-minor, semver-spec-minor, scalafix-migrations, old-version-remains, commit-count:n:2

@scala-steward scala-steward force-pushed the update/scalatest-3.2.19 branch from d5309f5 to 2450721 Compare September 18, 2024 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants