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

chore(deps): update dependency com.google.errorprone:error_prone_core to v2.33.0 #173

Merged

Conversation

renovate-bot
Copy link
Contributor

@renovate-bot renovate-bot commented Sep 30, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
com.google.errorprone:error_prone_core (source) 2.32.0 -> 2.33.0 age adoption passing confidence

Release Notes

google/error-prone (com.google.errorprone:error_prone_core)

v2.33.0: Error Prone 2.33.0

Similar to release 2.32.0, the minimum supported JDK version to run Error Prone is JDK 17 (#​3803). Using Error Prone to compile code that is deployed to earlier versions is still fully supported, but will require using JDK 17 or newer for compilation and setting --release or -source/-target/-bootclasspath.

Changes:

New checks:

Full changelog: google/error-prone@v2.32.0...v2.33.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@nielm nielm merged commit 0e1a876 into cloudspannerecosystem:main Oct 5, 2024
5 checks passed
@renovate-bot renovate-bot deleted the renovate/error-prone.version branch October 5, 2024 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants