@danielbankhead can we prioritize this, or at least release it as a patch? It is currently breaking production environments, especially for projects with automatic dependency updates.

Much appreciated 🙏.

🤖 Release is at https://github.com/googleapis/google-auth-library-nodejs/releases/tag/v9.4.0 🌻

Triggered job: cloud-devrel/client-libraries/nodejs/release/googleapis/google-auth-library-nodejs/publish (2023-11-30T15:22:40.844Z)

To trigger again, remove the autorelease: triggered label (in a few minutes).

The release build has started, the log can be viewed here. 🌻

🥚 You hatched a release! The release build finished successfully! 💜

Any plans for an RCA for what happened here? Tracking this down was incredibly difficult last night, and I had to make some substantial changes to my backend to get around it until today's patch.

Was there some place I'm not aware of to have tracked this issue? I didn't see anything reported on GCP's status page

@austinkline typically we have renovatebot update our dependencies, however it hasn’t triggered for this dep (investigating). Additionally, a fresh install of this library would have pulled in the updated gcp-metadata library, which is how it passed in our testing environment.

@austinkline typically we have renovatebot update our dependencies, however it hasn’t triggered for this dep (investigating). Additionally, a fresh install of this library would have pulled in the updated gcp-metadata library, which is how it passed in our testing environment.

Can you clarify what you mean by a fresh install? I tried to pull in the newest version of the auth library last night but it gave us no relief and so I had to offload all connections to other GCP services (pub/sub for us) from cloud functions somewhere else. Now that I've pulled in 9.4.0, I see the gcp-metadata version being bumped with it as well.

Can you clarify what you mean by a fresh install? I tried to pull in the newest version of the auth library last night but it gave us no relief

rm -rf node_modules package-lock.json && npm i

so I had to offload all connections to other GCP services (pub/sub for us) from cloud functions somewhere else

That’s rough; I’ll investigate this dependency update failure to reduce the risk of this happening in the future.