fix(release): validate compatibility updates for selected consumers

[f0rr0]

Release PR preparation rejected valid compatibility updates when a selected consumer still pinned an older runtime. For example, pg_hashids moved its pin from 0.3.0 to 0.3.2 while the runtime advanced from 0.3.1 to 0.3.2.

Bind compatibility edits to the selected consumer and its source product's exact version in the candidate manifest. Handle JSON, TOML, raw version files, and Rust constants through the shared validator. Reject edits to unselected consumers, incorrect pins, and unrelated settings. Update older fixtures to reflect independent consumer releases.

Validation:

• Release-tool formatting, lint, metadata, and the complete regression suite pass (including independent SDK pins).
• Reproduced the reported failure with a regression fixture before the fix.
• Generated the actual Release Please candidate from the failed run's exact main commit, e918d6a, and replayed the complete local closure with the controller fix: structured commit validation, consumer compatibility, and publication metadata passed for all 21 selected products.

After merge, run prepare-release-pr on the new main commit. The failed run used the old validator and cannot pick up this fix on rerun.

Exact-head CI run 37567234907 is running for commit c7a28dab6c24d5064a3f053976a4c134ccc9d833.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
oliphaunt-docs	Skipped		Oct 7, 2026 3:32am UTC