janhoy opened a new pull request, #4323:
URL: https://github.com/apache/solr/pull/4323

   https://issues.apache.org/jira/browse/SOLR-18206
   
   This PR supersedes apache/solr#4098 (originally opened by Renovate/SolrBot) 
and expands its scope significantly.
   
   Instead of just bumping individual Google Cloud library versions, this PR 
switches the GCS repository module to resolve all Google Cloud dependencies via 
the **`google-cloud-bom`** Bill of Materials, then bumps the BOM to the latest 
version (`0.261.0`). This simplifies future upgrades — only the BOM version 
needs updating, and all transitive Google Cloud
   libraries are automatically aligned.
   
   ### Changes
   
   - **`google-cloud-bom`** bumped from `0.224.0` → `0.261.0`
   - Removed explicit version pins for Google Cloud libraries now managed by 
the BOM (`google-cloud-storage`, `google-cloud-nio`, `google-cloud-core`, 
`google-cloud-core-http`, `google-auth`, `google-api-gax`)
   - Excluded unnecessary Google OTel transitive dependencies pulled in by the 
GCS module
   - Added `consistentResolution.useCompileClasspathVersions()` to the GCS 
module to align dependency resolution across configurations
   - Updated all lockfiles and license SHA1 files accordingly
   
   ### Key transitive version changes (via BOM 0.261.0)
   
   | Library | Before | After |
   |---|---|---|
   | `google-cloud-storage` | 2.27.0 | 2.67.0 |
   | `google-cloud-nio` | 0.127.3 | 0.131.0 |
   | `google-cloud-core` | 2.60.1 | 2.69.0 |
   | `google-auth` | 1.19.0 | 1.46.0 |
   | `gax` | 2.70.x | 2.79.0 |
   | `grpc-*` | 1.65.1 | 1.80.0 |


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to