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

chore: Update scalamock from 5.2.0 to 6.0.0 #845

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

scala-steward
Copy link
Contributor

@scala-steward scala-steward commented Apr 8, 2024

About this PR

πŸ“¦ Updates org.scalamock:scalamock from 5.2.0 to 6.0.0 ⚠

πŸ“œ 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!

πŸ” Files still referring to the old version number

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

CHANGELOG.md
build.sc
βš™ Adjust future updates

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

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

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

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalamock", artifactId = "scalamock" }
}]
labels: library-update, early-semver-major, semver-spec-major, old-version-remains, commit-count:1

@scala-steward scala-steward force-pushed the update/scalamock-6.0.0 branch 2 times, most recently from 2f89dd7 to 6062d78 Compare April 21, 2024 15:02
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.

None yet

1 participant