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

bump: play-json 2.10.6 (was 2.9.4) #3225

Closed

Conversation

scala-steward
Copy link
Contributor

@scala-steward scala-steward commented Jul 10, 2024

About this PR

πŸ“¦ Updates com.typesafe.play:play-json from 2.9.4 to 2.10.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!

βš™ Adjust future updates

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

updates.ignore = [ { groupId = "com.typesafe.play", artifactId = "play-json" } ]

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

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.typesafe.play", artifactId = "play-json" }
}]
labels: test-library-update, early-semver-minor, semver-spec-minor, commit-count:1

@probot-autolabeler probot-autolabeler bot added the dependency-change For PRs changing the version of a dependency. label Jul 10, 2024
@ennru
Copy link
Member

ennru commented Sep 30, 2024

As we EOL Couchbase, this seems irrelevant.

@ennru ennru closed this Sep 30, 2024
@scala-steward scala-steward deleted the update/play-json-2.10.6 branch October 2, 2024 13:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependency-change For PRs changing the version of a dependency.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants