ci: reduce release-please commit batch size

[fan-zhang-sv]

Summary

• Configure release-please to fetch commit history one commit per GitHub GraphQL request.
• Work around repeated GitHub GraphQL internal errors while release-please is collecting merge commits on master.

Why

The release-please workflow is failing before any package build or npm publish step. The logs show release-please successfully loading config, finding the latest releases for both packages, and then failing while paging merge commits through GitHub GraphQL:

✔ Collecting commits since all latest releases
❯ Fetching merge commits on branch master with cursor: ...
Error: release-please failed: Request failed due to following response errors:
 - Something went wrong while executing your query ...

That Something went wrong while executing your query / E001 response is a GitHub GraphQL internal error. In this case, it is happening while release-please is fetching commit history, so reducing the per-request commit batch size makes each GraphQL query smaller and less likely to timeout or hit a GitHub-side execution failure.

Source For The Fix

Release-please v17.3.0 added commit-batch-size specifically to make commit-history pagination configurable:

• Release notes: https://github.com/googleapis/release-please/releases/tag/v17.3.0
• Upstream PR: feat: add ability to configure how many commits we retrieve when iterating through repo history googleapis/release-please#2679

The upstream PR describes the same failure mode: release-please consistently hitting GitHub GraphQL 502/internal errors while querying repository history, and succeeding only after lowering the number of commits fetched per request.

Tradeoff

Setting commit-batch-size to 1 increases the number of GitHub API calls, so the release-please job may run slower. The benefit is that each GraphQL request is much smaller, which should make the workflow more reliable for the current failure.

Test plan

• Validated release-please-config.json parses as JSON.
• Existing CI will run on the PR.

[cb-heimdall]

✅ Heimdall Review Status

Requirement	Status	More Info
Reviews	✅ 2/1	Denominator calculation Show calculation 1 if user is bot 0 1 if user is external 0 2 if repo is sensitive 0 From .codeflow.yml 1 Additional review requirements Show calculation Max 0 0 From CODEOWNERS 0 Global minimum 0 Max 1 1 1 if commit is unverified 0 Sum 1

[github-actions]

PR title: ci: reduce release-please commit batch size — valid conventional commits format, no change needed.

Summary: This is a single-line config change adding "commit-batch-size": 1 to release-please-config.json to work around GitHub GraphQL internal errors during release-please commit history pagination. No code, type, API surface, or bundle size impact.

One minor observation: commit-batch-size: 1 is the most extreme setting — one GraphQL request per commit. If the release-please job becomes noticeably slow (e.g., after many commits accumulate between releases), consider bumping this to 5 or 10 as a middle ground. Not a blocking concern — starting at 1 for reliability and tuning up later is a reasonable approach.

No blocking issues found.

[spencerstock]

LGTM