[cld-sec]

Snyk has created this PR to upgrade org.hibernate:hibernate-validator-annotation-processor from 6.0.1.Final to 6.2.6.Final.

ℹ️ 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 44 versions ahead of your current version.

• The recommended version was released 25 days ago.

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

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

[cld-sec]

This is a minor version upgrade from Hibernate Validator 6.0.1.Final to 6.2.6.Final. While it does not require a major namespace migration, it introduces several changes that warrant a medium risk assessment.

Key Changes:

• javax.validation Namespace: This version range continues to use the javax.validation namespace, so no migration to jakarta.validation is required. Support for the jakarta.validation namespace was added in 6.1, but the primary artifacts still use the older namespace.
• @SafeHtml Removal: The @SafeHtml constraint, which was previously deprecated, has been removed in version 6.2. If your application uses this constraint, you will need to find an alternative.
• Expression Language (EL) Changes: Version 6.2 brought an overhaul to Expression Language handling, disabling it by default for custom violations to improve security. This could affect custom constraint violation messages that rely on EL expressions.
• Java Version: Requires Java 8 or higher, which is consistent with version 6.0.

Recommendation:

• Review your codebase for any usage of the now-removed @SafeHtml constraint.
• Verify that any custom constraint violations that use Expression Language are still functioning as expected.
• As with any dependency upgrade, it is recommended to run a full regression test suite to catch any unexpected behavioral changes from bug fixes and improvements.

Source: Hibernate Validator 6.2 Release Notes

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