[Snyk] Upgrade com.fasterxml.jackson.datatype:jackson-datatype-jsr310 from 2.15.3 to 2.20.1

[sajith-subramanian]

Snyk has created this PR to upgrade com.fasterxml.jackson.datatype:jackson-datatype-jsr310 from 2.15.3 to 2.20.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 26 versions ahead of your current version.

• The recommended version was released 2 months ago.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[Copilot]

Pull request overview

This PR upgrades the Jackson datatype library from version 2.15.3 to 2.20.1, advancing 26 versions to address dependency updates and potentially include bug fixes and security improvements.

Key Changes

• Updates the Jackson version property in the Maven POM configuration
• Applies to the jackson-datatype-jsr310 dependency used for Java 8 date/time type handling

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sajith-subramanian]

This is a minor version upgrade across several versions (2.15.3 → 2.20.1). While Jackson aims for backward compatibility in minor releases, this update includes significant internal changes that warrant caution.

• Jackson 2.17: Introduced stricter parsing for numbers represented as strings (e.g., values with leading zeroes like "07" may no longer deserialize as numbers). [1]
• Jackson 2.18: Contained a major internal rewrite of the POJO (Plain Old Java Object) property introspection logic. [22] While intended to fix bugs, this could introduce subtle behavioral changes.

Source: Jackson Release Notes
Recommendation: No specific API migration is required, but thorough regression testing is strongly recommended to validate serialization and deserialization behavior, especially for complex objects and edge cases.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.