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 slf4j-log4j12 from 2.0.13 to 2.0.16 #3735

Closed
wants to merge 1 commit into from

Conversation

RenkuBot
Copy link
Collaborator

About this PR

πŸ“¦ Updates org.slf4j:slf4j-log4j12 from 2.0.13 to 2.0.16

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 = "org.slf4j", artifactId = "slf4j-log4j12" } ]

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

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.slf4j", artifactId = "slf4j-log4j12" }
}]
labels: test-library-update, early-semver-patch, semver-spec-patch, commit-count:1

@RenkuBot RenkuBot requested a review from a team as a code owner August 13, 2024 06:02
@eikek eikek changed the base branch from master to release-0.57.0 August 13, 2024 08:49
@eikek eikek requested review from a team as code owners August 13, 2024 08:49
@eikek eikek changed the base branch from release-0.57.0 to master August 13, 2024 08:50
@eikek eikek closed this Sep 17, 2024
@eikek eikek deleted the update/slf4j-log4j12-2.0.16 branch September 17, 2024 08:41
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.

2 participants