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

logback-core 1.5.0 (was 1.4.14) #846

Merged
merged 1 commit into from
Feb 26, 2024

Conversation

scala-steward
Copy link
Contributor

About this PR

πŸ“¦ Updates ch.qos.logback:logback-core from 1.4.14 to 1.5.0

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 = "ch.qos.logback", artifactId = "logback-core" } ]

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

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "ch.qos.logback", artifactId = "logback-core" }
}]
labels: test-library-update, early-semver-minor, semver-spec-minor, commit-count:1

@mergify mergify bot added the type:updates label Feb 20, 2024
@ihostage
Copy link
Member

https://logback.qos.ch/news.html#1.5.0

I don't see a reason not to merge that.
@mkurz WDYT?

@mkurz
Copy link
Member

mkurz commented Feb 26, 2024

@ihostage yes I was also looking at the diff qos-ch/logback@v_1.4.14...v_1.5.0 and I think it's safe. Also they say on the news page

The 1.5.x series is a direct descendant of and a drop-in replacement for the 1.4.x series

So I think we can upgrade and should be fine.

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.

3 participants