Move workflows to Node 22 and upgrade googleapis to 186 #123

❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Overview

Dependabot PR #120 bumps googleapis from 142.0.0 to 186.0.0. It can't land yet: googleapis declares engines.node: >=22.0.0 from 178.1.1, and every workflow here runs Node 20. yarn install --frozen-lockfile rejects Node 20.20.2 (run).

Complexity: Low
Target branch: main

Context

• googleapis is a production dependency, used only by scripts/update-pr-spreadsheet.js (google.auth.GoogleAuth and google.sheets v4).
• None of the per-API breaking changes in 143–186 touch sheets. The Sheets calls in the script work as they are.
• The bump also moves transitive dependencies up a major version: google-auth-library 9 → 11, googleapis-common 7 → 9, gaxios 6 → 8, gcp-metadata 6 → 9 and node-fetch 2 → 3.

The Change

• Every actions/setup-node step in .github/workflows/ should use Node 22. There are 16 files, all pinned to '20' or 20. They all install from the one yarn.lock, so a single workflow left on Node 20 still fails once the lockfile requires Node 22.
• googleapis should then be upgraded to 186.0.0 or later. Rebasing or recreating Bump googleapis from 142.0.0 to 186.0.0 #120 does this.

Acceptance Criteria

• No workflow in .github/workflows/ sets node-version below 22.
• package.json and yarn.lock resolve googleapis to ≥186.0.0.
• yarn install --frozen-lockfile, yarn lint and yarn test pass in CI.
• A dry_run dispatch of the "Update community pull requests spreadsheet" workflow completes on Node 22.

AI usage

rtibblesbot, an LLM-based coding agent, reviewed #120, recommended closing it, and drafted this issue from that review and the repository's workflows and lockfile.

Filed from #120's review.