Why didn't a check detect the inconsistent protobuf version 3.23.3 when the shared dependencies BOM had 3.23.2? #2621
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Why didn't a check detect the inconsistent protobuf version 3.23.3 when the shared dependencies BOM had 3.23.2?
Detecting the discrepancy in java-cloud-bom is late https://github.com/googleapis/java-cloud-bom/actions/runs/8476531114/job/23226189124. That discrepancy should have been detected within this repository.
In the pull request #2570, Guava version was caught #2570 (comment).
The text was updated successfully, but these errors were encountered: