Skip to content
Open
Changes from all commits
Commits
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 sdkmanager/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -120,7 +120,7 @@
<maven.compiler.target>17</maven.compiler.target>
<resilience4j.version>2.2.0</resilience4j.version>
<httpcomponents.version>5.5</httpcomponents.version>
<jackson.version>2.15.3</jackson.version>
<jackson.version>2.18.6</jackson.version>
Copy link

Copilot AI Mar 2, 2026

Choose a reason for hiding this comment

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

sdkmanager now upgrades jackson.version to 2.18.6, but datamanagement/pom.xml still pins its own jackson.version to 2.15.3 for jackson-datatype-jsr310. This can lead to mixed Jackson artifacts (and potentially reintroduce the vulnerable version via dependency resolution) when consumers depend on both modules. Consider aligning all Jackson artifacts across the repo (e.g., bump datamanagement’s jackson.version too, or manage Jackson versions via a shared parent/BOM).

Copilot uses AI. Check for mistakes.
<slf4j.version>2.0.9</slf4j.version>
<logback.version>1.4.12</logback.version>
</properties>
Expand Down