Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to Lombok 1.18.32 #40050

Closed
wants to merge 1 commit into from
Closed

Upgrade to Lombok 1.18.32 #40050

wants to merge 1 commit into from

Conversation

anbusampath
Copy link

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Mar 21, 2024
@bclozel
Copy link
Member

bclozel commented Mar 21, 2024

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.

@bclozel bclozel closed this Mar 21, 2024
@bclozel bclozel added status: invalid An issue that we don't feel is valid and removed status: waiting-for-triage An issue we've not yet triaged labels Mar 21, 2024
@anbusampath anbusampath deleted the patch-1 branch March 21, 2024 12:05
@anbusampath
Copy link
Author

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.

@wilkinsona
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: invalid An issue that we don't feel is valid
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants