Repository navigation
Conversation
Co-authored-by: phlax <454682+phlax@users.noreply.github.com>
Co-authored-by: phlax <454682+phlax@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add automation for upstream Envoy-org release registration
Automate upstream release registration from .bcr templates
Oct 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add deterministic registration of Envoy-org releases, initially examples, using upstream
.bcr/files. Missing dependencies, dropped patches/overlays, or ambiguous inputs abort without writing entries or opening a PR.register-moduledispatches, validate inputs before authentication, and open registration PRs through pinned toolshed actions aspublish-envoy[bot]..envoyversus manual.envoy.Nversions; add mocked-network tests to registry CI.Example dispatch payload:
{"repository":"envoyproxy/examples","ref":"v0.2.10","version":"0.2.10","dry-run":false}The examples dry-run matches source integrity; upstream presubmits and unrelated MODULE whitespace are preserved rather than reproducing manual-entry differences. No
modules/changes are included. Producer-side dispatch hooks remain follow-up work.