chore(deps): bump slf4j from 1.7.30 to 2.0.18 - #6053
Conversation
Bumps `slf4j` from 1.7.30 to 2.0.18. Updates `org.slf4j:slf4j-api` from 1.7.30 to 2.0.18 Updates `org.slf4j:slf4j-jdk14` from 1.7.30 to 2.0.18 --- updated-dependencies: - dependency-name: org.slf4j:slf4j-api dependency-version: 2.0.18 dependency-type: direct:production update-type: version-update:semver-major - dependency-name: org.slf4j:slf4j-jdk14 dependency-version: 2.0.18 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 6ac2a61. Configure here.
| sqlite = "2.6.2" | ||
| sqliteRc = "2.7.0-rc01" # Required by Room3 3.0.0-rc* | ||
| slf4j = "1.7.30" | ||
| slf4j = "2.0.18" |
There was a problem hiding this comment.
SLF4J 2.x breaks Logback 1.2
High Severity
Bumping the slf4j catalog version from 1.7.30 to 2.0.18 is a breaking major upgrade. logback stays at 1.2.9, which only implements the SLF4J 1.7 StaticLoggerBinder SPI, so SLF4J 2.x finds no provider. sentry-jul tests then get a no-op MDC, and context tags are dropped.
Reviewed by Cursor Bugbot for commit 6ac2a61. Configure here.
|
Guessing we can't bump this now |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
1 participant
Bumps
slf4jfrom 1.7.30 to 2.0.18.Updates
org.slf4j:slf4j-apifrom 1.7.30 to 2.0.18Updates
org.slf4j:slf4j-jdk14from 1.7.30 to 2.0.18Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)