You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure what the best approach would be to changing the dependencies to the new artifact but wanted to make sure it was known as the old repository now have a CRITICAL CVE related to it (https://nvd.nist.gov/vuln/detail/CVE-2024-49203). I'm not sure what changed or if this will affect any potential autoconfigurations currently used, but I wanted to make sure the team is aware.
The text was updated successfully, but these errors were encountered:
Thanks for suggestion, but we're going to need to follow Spring Data's lead here. There's a (currently closed) issue discussing things at spring-projects/spring-data-jpa#3335
- junit-bom is already imported by the spring boot bom (5.10.2)
- hibernate-core is already managed by the spring boot bom (6.4.3.Final)
- querydsl-apt and querydsl-jpa are missing the jakarta classifier
Related: spring-projects/spring-boot#43550
The Spring Boot Dependencies contains a reference to the following dependency:
This dependency has now changed to this repository with the following Maven coordinate:
I'm not sure what the best approach would be to changing the dependencies to the new artifact but wanted to make sure it was known as the old repository now have a CRITICAL CVE related to it (https://nvd.nist.gov/vuln/detail/CVE-2024-49203). I'm not sure what changed or if this will affect any potential autoconfigurations currently used, but I wanted to make sure the team is aware.
The text was updated successfully, but these errors were encountered: