Skip to content

chore: bump ch.qos.logback:logback-classic from 1.2.3 to 1.6.4 #58

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.

Sign up for GitHub

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

Closed
dependabot wants to merge 1 commit into from
Closed

chore: bump ch.qos.logback:logback-classic from 1.2.3 to 1.6.4 #58

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion build.gradle
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ ext {
threetenbp_version = "1.3.5"
json_fire_version = "1.8.0"
slf4j_core_version = "1.6.3"
slf4j_classic_version = "1.2.3"
slf4j_classic_version = "1.6.4"

@cursor cursor Bot Sep 30, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Logback core and classic version mismatch

High Severity

logback-classic is bumped to 1.6.4 via slf4j_classic_version, but logback-core remains at 1.6.3 via slf4j_core_version. Logback requires these two artifacts to be at the exact same version. A mismatch can cause startup failures, NoSuchMethodError, or NPEs in VersionUtil.checkForVersionEquality. The slf4j_core_version needs to be bumped to 1.6.4 as well.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit a324529. Configure here.

slf4j_version = "2.0.18"
}

Expand Down
Loading