[Lewis-Clayton]

Summary

Upgrades the library to Google Ads API v26.1, depending on google-ads-node@26.1.0-beta.0, google-gax@^6.16.0 and google-auth-library@^11.3.3. The version 26.1.0-beta.0 goes out under the beta dist-tag for testing ahead of the stable release.

As a new major, this release also makes the package ES module-only, which lets it move to stream-json 3 (#554), makes developer_token optional (#550), and fixes a set of long-standing defects whose fixes change method shapes. CHANGELOG.md lists every breaking change with what to change in calling code.

Version upgrade

• google-ads-api → v26.1; google-ads-node → v26.1.0; google-gax → v6.16.0; google-auth-library → v11.3.3; stream-json → v3; esbuild → v0.28
• New services CustomerBudgetNetworkSettingService and LocalServicesEligibilityService, two new resource names and 15 new enums
• v26 removes the hotel criteria on ad_group_bid_modifier and customer.conversion_tracking_setting.enhanced_conversions_for_leads_enabled

Packaging

• "type": "module" with a single tsc build and an export map of types + default, so require("google-ads-api") keeps working on Node 22.12+ through require(esm) and returns the same module instance as import
• tests/package.mjs asserts the require/import identity, and tests/package.cjs loads the package with a cold require() in its own process; arethetypeswrong runs with --profile esm-only
• TypeScript CommonJS consumers need module: "nodenext" (TypeScript 5.8+) or "node20" (TypeScript 5.9+); node16 and node18 report TS1479
• Jest in CommonJS mode needs ESM mode or a transform of google-ads-api, stream-json and stream-chain (ts-jest with allowJs and esModuleInterop); the changelog carries a config verified on Jest 29 and 30
• CI also type-checks the generator scripts (tsc -p tsconfig.json); files excludes build/*.tsbuildinfo

Breaking changes

• ES modules only and Node.js 22.12+ (see Packaging)
• Mutate helpers for the ten single-operation services (customers, customerClientLinks, billingSetups…) take one resource instead of an array
• Mutation hooks receive mutateOptions on every path; BaseMutationHookArgs requires it
• Update helpers build the update mask from the plain object passed in: [] clears a repeated field, null clears a field, undefined leaves it alone (in mutateResources too), and a key that names no field reaches the API
• queryStream, reportStream and reportStreamRaw take StreamRequestOptions / ReportStreamOptions; streams request summary rows with summary_row_setting; stream hooks receive ReportStreamOptions, query hooks keep ReportOptions
• query and report send page_token and validate_only to search, and enforce max_reporting_rows on decoded rows; query hooks no longer write into the caller's options
• REST results parse repeated enum and INT64 fields, keep enum names and numbers this version does not know, and take each field's type from its exact proto message (recommendation budget micros now parse as numbers)
• REST errors become GoogleAdsFailures only when a detail's @type names one; every other REST failure surfaces as an Error with the API message (or the axios code and HTTP status) as cause, never the axios error
• Paginated service methods return one page as the RPC response; long-running methods carry LROperation types
• LocalServices getters now read localServicesLeads and localServicesEligibilities
• ClientOptions["developer_token"] has the type string | undefined

Fixes

• Error "Mutate operations must have 'create', 'update', or 'remove' specified" while creating account budget #289, Error "Mutate operations must have 'create', 'update', or 'remove' specified" while creating customer client links #316, Unable to mutate billing setups #501, Unable to create new CustomerClientLink #518: single-operation mutate helpers sent operations, which protobuf serialisation dropped, so the API received only customer_id
• Make developer_token optional and omit the header when unset #550, developer_token: Google documents it as sunset and ignored, but the API still rejects requests without one #553: no developer-token header when the token holds nothing, an empty string or only whitespace
• REST errors no longer carry the OAuth access token or developer token: 25.x rethrew axios errors whose config.headers held both
• REST access tokens refresh at their real expiry instead of after a fixed 50 minutes, and concurrent calls with the same refresh token share one refresh
• Every gRPC call gets its own metadata; without call headers, google-gax shared one Metadata object across calls, so in-place instrumentation leaked trace headers between requests
• Mutation hooks could not see validate_only for mutateResources, so a hook could not tell a dry run from a real mutation
• mutateResources keeps policy exemption keys when operation defaults to create
• Update helpers clear repeated fields set to []
• REST errors without failure details, or with google.rpc.ErrorInfo details, keep their diagnostic instead of a TypeError or an empty GoogleAdsFailure
• The field-type generator resolves types by full proto name, which fixes Performance Max listing-group parsing and the recommendation and accessible bidding strategy types
• The lockfile resolves patched @grpc/grpc-js 1.14.7, follow-redirects, brace-expansion and fast-uri; yarn audit reports nothing for runtime dependencies

Test plan

• yarn lint, tsc -p tsconfig.json, yarn test (276 tests) and yarn test:package on Node 22.23 and 24.21
• arethetypeswrong --profile esm-only on the packed tarball; a fresh project loads the tarball through both require() and import
• Each fix has a regression test that fails without it
• Jest 29 and 30 consumers load the package with the changelog's transform and in ESM mode; TypeScript 5.9 consumers type-check under nodenext and node20
• Publish 26.1.0-beta.0 under the beta dist-tag and test downstream
• Update to google-ads-node 26.1.0 and version 26.1.0 after review
• Publish 26.1.0 under the latest dist-tag

[chatgpt-codex-connector]

Codex Review Summary: ❌ Failed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	❌ Failed 2026-11-06T09:49:28.862313Z We couldn’t complete this review. Comment @codex review to try again.	348cf75	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.