https://projectlombok.org/changelog - Initial JDK22 support added. https://github.com/projectlombok/lombok/issues/3630
Comment From: bclozel
Thanks, but there is no need to to provide PRs for dependency upgrades, especially if no code change is required.
As mentioned in our issue template:
You DO NOT need to raise an issue for a managed dependency version upgrade as there's a semi-automatic process for checking managed dependencies for new versions before a release.
We will perform upgrades matching our 3rd party upgrade policy. If this is an urgent matter for you, there is no need to wait for us releasing as you can use a Gradle or Maven build property to override the library version. All version properties are listed in the reference documentation appendix.
Comment From: anbusampath
I am sorry, I should have asked in other channel before raising his the PR. I know about the automated process, but lombok 1.18.32 released yesterday and didn't picked up. When run on Java 22, It caused some issue in IDE and build.
Comment From: wilkinsona
Unfortunately, it narrowly missed today's releases. If you're using Lombok and Java 22, you should override the version as Brian has described above.