Yes, the issue appears to be a bug introduced in latest spring 3.4.1 released on 19th Dec 2024. Two possible workarounds are,

1. Downgrading spring-boot to 3.4.0 by changing the version in pom.xml file and reloading the maven changes.
2. Removing spring dev-tools dependency from pom.xml file if you want to continue to use spring 3.4.1

(Ref: https://www.udemy.com/course/spring-hibernate-tutorial/learn/lecture/36836512#questions/22798063)