Quicker way to release GAX and google auth library together?

@Neenu1995

As of now, when the google auth library provides a new method for GAX, we need to release Google Cloud BOM and the Libraries BOM that contains the newer version of the google auth library. Until that, GAX cannot use the google auth library because Linkage Monitor complains:

googleapis/gax-java#1420 (comment)

Once the Libraries BOM release is done, we can upgrade the google auth library version in GAX.

Is there a better way?

CC: @Neenu1995

How often does this happen? If it's a once a year thing, we might as well just push libraries-bom.

This is also an argument for not necessarily waiting for google-cloud-bom to update the auth-library before libraries-bom does.

Yes, it's rare. For this case, Neenu is going to release the Google Cloud BOM (with new dependencies BOM), and we'll release the Libraries BOM.

I'll record occurrences in this issue in case similar situation happens again.

Also I'm wondering whether Linkage Monitor is a suitable tool here now. The Libraries BOM now follows the Google Cloud BOM and the shared dependencies BOM.

While Linkage Monitor might find some unexpected dependency problems, the main purpose of finding incompatible dependencies are handled by the full convergence check at java-cloud-bom repository.

(I have not decided anything yet.)

ci: removing linkage-monitor from the required checks

ci: removing linkage-monitor from the required checks (#1513)

ci: removing linkage-monitor from the required checks (#501)

ci: removing linkage-monitor from the required checks (#1003)

ci: removing linkage-monitor from the required checks (#663)

ci: removing linkage-monitor from the required checks (#811)

ci: removing linkage-monitor from the required checks (#203)

ci: removing linkage-monitor from the required checks (#652)

ci: removing linkage-monitor from the required checks (#574)

ci: removing linkage-monitor from the required checks (#521)

ci: removing linkage-monitor from the required checks (#588)

ci: removing linkage-monitor from the required checks (#135)

ci: removing linkage-monitor from the required checks (#86)

ci: removing linkage-monitor from the required checks (#95)

ci: removing linkage-monitor from the required checks (#41)

ci: removing linkage-monitor from the required checks (#552)

fyi, linkage-monitor check failed for a reason similar to this in googleapis/java-datastore#492

@aristide-n

@aristide-n Yes, as you might already noticed, I've removed the check from the required checks of these repositories. For java-datastore, it's done googleapis/java-datastore#515.

ci: removing linkage-monitor from the required checks (#56)