Skip to content

v6: proto-sync automation — commons dispatch -> regen PR #46

Description

@Pandys

The pipeline that kills feature lag. Two halves:

commons repo:

  • Workflow on proto tag push: repository_dispatch to this repo (event protos-updated, payload {ref})

this repo:

  • Workflow on that dispatch: checkout commons @ ref, update COMMONS_VERSION, buf generate, run tests, open PR "chore: sync protos " with the regen diff
  • Nightly scheduled sync as safety net for missed dispatches
  • buf breaking already gates commons, so syncs are additive in the normal case; a breaking change fails the PR loudly for a human decision (usually: major bump)

Checks fully automatic; releasing is a separate, human-gated step (release-pipeline issue).

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestpriority: mediumNeeded for release, not blocking corev6v6 rewrite (Major/6)

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions