Skip to content

chore: bump jackson to 2.18.10 and logback to 1.3.16 #22

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

Open
Vligai wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: bump jackson to 2.18.10 and logback to 1.3.16 #22

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
10 changes: 5 additions & 5 deletions pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,17 +67,17 @@
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-core</artifactId>
<version>2.17.1</version>
<version>2.18.10</version>
</dependency>
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-databind</artifactId>
<version>2.17.1</version>
<version>2.18.10</version>
</dependency>
<dependency>
<groupId>com.fasterxml.jackson.datatype</groupId>
<artifactId>jackson-datatype-jsr310</artifactId>
<version>2.17.1</version>
<version>2.18.10</version>
</dependency>
<!-- Annotation dependencies-->
<dependency>
Expand All @@ -91,7 +91,7 @@
<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-core</artifactId>
<version>1.3.14</version>
<version>1.3.16</version>

@greptile-apps greptile-apps Bot Sep 9, 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.

P2 Logback Advisories Remain

This upgrade does not clear the Logback advisories described by the PR: logback-core and logback-classic 1.3.16 remain affected by the three identified 2026 advisories. Both dependencies are compile-scoped even though production code does not use Logback, so SDK consumers still receive the affected artifacts transitively and dependency scans will continue to report them. Consider removing the unused logging dependencies or choosing a compatible remediation strategy.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

</dependency>

<dependency>
Expand All @@ -104,7 +104,7 @@
<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-classic</artifactId>
<version>1.3.14</version>
<version>1.3.16</version>
</dependency>

<!-- HTTP request dependencies-->
Expand Down
Loading