Conversation
WalkthroughThis PR updates two dependency versions in the Gradle version catalog. The errorprone-plugin is bumped from 5.0.0 to 5.1.0, and the errorProne dependency is bumped from 2.47.0 to 2.48.0. These are version-only updates with no changes to library additions, removals, or public API signatures. Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs). Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@gradle/libs.versions.toml`:
- Line 18: The specified Error Prone version "errorProne" = "2.48.0" is not
available on Maven Central and will break dependency resolution; update the
value in gradle/libs.versions.toml to a published release (e.g., "2.47.0") or
temporarily pin to the last known-good version, then run dependency
resolution/build to verify; alternatively revert the change until Maven Central
syncs. Ensure you update the "errorProne" entry and re-run the Gradle build to
confirm the fix.
- Line 12: Update the Error Prone library version in gradle/libs.versions.toml:
change the errorprone library version entry (the errorprone version key that
pairs with the net.ltgt.errorprone plugin) from 2.48.0 to the published 2.47.0
so the build can resolve the artifact; leave errorprone-plugin = "5.1.0"
unchanged.
| gradle-maven-publish-plugin = "0.34.0" | ||
| spotless = "8.2.1" | ||
| errorprone-plugin = "5.0.0" | ||
| errorprone-plugin = "5.1.0" |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
net.ltgt.errorprone Gradle plugin version 5.1.0
💡 Result:
net.ltgt.errorprone Gradle plugin version 5.1.0 is published on the Gradle Plugin Portal and is currently listed as latest (created February 28, 2026). [1]
Apply with plugins DSL:
plugins {
id("net.ltgt.errorprone") version "5.1.0"
}[1]
Artifact coordinate (for convention plugins / buildscript classpath):
implementation("net.ltgt.errorprone:net.ltgt.errorprone.gradle.plugin:5.1.0")[1]
Minimum requirements (per project README): at least Gradle 6.8, and JDK 11 for compilation. [2]
Sources: [1] [2]
🌐 Web query:
Error Prone library version 2.48.0 Maven Central
💡 Result:
com.google.errorprone version 2.48.0 is not present on Maven Central (as of Feb 28, 2026). The Maven Central directory listing for error_prone_core shows releases up through 2.47.0 (released Feb 5, 2026) and does not include 2.48.0. [1] MvnRepository also lists 2.47.0 as the latest error_prone_core version on Central. [2]
If you meant the latest available on Central, use 2.47.0 (example):
<dependency>
<groupId>com.google.errorprone</groupId>
<artifactId>error_prone_core</artifactId>
<version>2.47.0</version>
</dependency>[1] https://repo1.maven.org/maven2/com/google/errorprone/error_prone_core/
[2] https://mvnrepository.com/artifact/com.google.errorprone/error_prone_core
🏁 Script executed:
#!/bin/bash
# Verify versions via Maven Central and GitHub
# Check Error Prone library 2.48.0
echo "=== Checking Error Prone library 2.48.0 ==="
curl -s "https://repo1.maven.org/maven2/com/google/errorprone/error_prone_core/maven-metadata.xml" | grep -o "2\.48\.0" | head -1
# Check plugin versions on Maven Central
echo "=== Checking net.ltgt.errorprone plugin versions ==="
curl -s "https://repo1.maven.org/maven2/net/ltgt/gradle/gradle-errorprone-plugin/maven-metadata.xml" | grep -oP '<version>\K[^<]*' | tail -5Repository: uber/NullAway
Length of output: 190
Plugin version 5.1.0 exists and is correct. The net.ltgt.errorprone plugin version 5.1.0 is published on the Gradle Plugin Portal and is the current latest release (as of February 28, 2026).
However, Error Prone library version 2.48.0 does not exist on Maven Central. The latest available version is 2.47.0 (released February 5, 2026). This PR will fail to build with the specified errorProne version. Update line 18 from 2.48.0 to 2.47.0, or verify if 2.48.0 should reference a different artifact/repository.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@gradle/libs.versions.toml` at line 12, Update the Error Prone library version
in gradle/libs.versions.toml: change the errorprone library version entry (the
errorprone version key that pairs with the net.ltgt.errorprone plugin) from
2.48.0 to the published 2.47.0 so the build can resolve the artifact; leave
errorprone-plugin = "5.1.0" unchanged.
| shellcheck = "1.5.0" | ||
|
|
||
| errorProne = "2.47.0" | ||
| errorProne = "2.48.0" |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify Error Prone 2.48.0 exists on Maven Central and check release notes
# Check if version exists on Maven Central
echo "=== Checking Maven Central for Error Prone 2.48.0 ==="
curl -s "https://search.maven.org/solrsearch/select?q=g:com.google.errorprone+AND+a:error_prone_core+AND+v:2.48.0&rows=1&wt=json" | jq '.response.numFound'
echo -e "\n=== Recent Error Prone releases from GitHub ==="
curl -s "https://api.github.com/repos/google/error-prone/releases" | jq -r '.[0:10] | .[] | "\(.tag_name): \(.published_at)"'
echo -e "\n=== Checking for v2.48.0 release details ==="
curl -s "https://api.github.com/repos/google/error-prone/releases/tags/v2.48.0" | jq '{tag_name, name, published_at, body}' 2>/dev/null || echo "Version v2.48.0 not found"Repository: uber/NullAway
Length of output: 1130
Error Prone 2.48.0 is not yet available on Maven Central.
The version has been released on GitHub (Feb 27, 2026) but is not yet indexed on Maven Central (returns 0 results). The build will fail due to dependency resolution failure. Wait for Maven Central synchronization or use an alternative version.
Note: The release includes new checks (AvoidValueSetter, UnnecessarySemicolon) that should be reviewed for compatibility with NullAway once the version is available.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@gradle/libs.versions.toml` at line 18, The specified Error Prone version
"errorProne" = "2.48.0" is not available on Maven Central and will break
dependency resolution; update the value in gradle/libs.versions.toml to a
published release (e.g., "2.47.0") or temporarily pin to the last known-good
version, then run dependency resolution/build to verify; alternatively revert
the change until Maven Central syncs. Ensure you update the "errorProne" entry
and re-run the Gradle build to confirm the fix.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1486 +/- ##
=========================================
Coverage 88.41% 88.41%
Complexity 2782 2782
=========================================
Files 99 99
Lines 9283 9283
Branches 1872 1872
=========================================
Hits 8208 8208
Misses 524 524
Partials 551 551 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
2 participants
Summary by CodeRabbit