buf-version-pinning

Unpinned Buf plugin versions cause large unrelated diffs in generated code because version bumps trigger wide regeneration across all outputs. Pinning plugin versions across buf.yaml, buf.lock, and buf.gen.yaml prevents this unintended drift and keeps generated code stable.

To pin Buf plugin versions, update the plugin version in buf.gen.yaml, run just gen to review the regen impact, then reconcile buf.lock with buf.yaml changes. This ensures generated outputs remain consistent and prevents downstream breakage for Connect-RPC, sqlc, and SDK consumers.

The best way to predict regen impact is to update the plugin version in buf.gen.yaml and run just gen to group diffs for downstream consumers. This surfaces compatibility concerns for Connect-RPC, sqlc, and SDK shapes before merging the changes.

You need to reconcile buf.lock with buf.yaml immediately after any Buf plugin version change to validate that dependencies align. This prevents drift across configuration files and ensures generated outputs remain consistent after regeneration.

Yes, pinning Buf plugin versions works with Connect-RPC and sqlc generated code. It stabilizes SDK shapes by preventing unintended diffs when configuration files change, requiring deliberate version updates and verification that generated outputs remain consistent.