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-jmh to 0.4.6 #3652

Merged
merged 1 commit into from
Oct 2, 2023
Merged

Update sbt-jmh to 0.4.6 #3652

merged 1 commit into from
Oct 2, 2023

Conversation

scalameta-bot
Copy link
Contributor

About this PR

πŸ“¦ Updates pl.project13.scala:sbt-jmh from 0.4.5 to 0.4.6

πŸ“œ 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 (0.4.5).
You might want to review and update them manually.

docs/CHANGELOG.md
βš™ Adjust future updates

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

updates.ignore = [ { groupId = "pl.project13.scala", artifactId = "sbt-jmh" } ]

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

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "pl.project13.scala", artifactId = "sbt-jmh" }
}]
labels: sbt-plugin-update, early-semver-minor, semver-spec-patch, old-version-remains, commit-count:1

@kitbellew kitbellew merged commit b63842c into master Oct 2, 2023
8 checks passed
@kitbellew kitbellew deleted the update/sbt-jmh-0.4.6 branch October 2, 2023 10:45
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