Skip to content

ci: derive component routing from the plugin registry - #15

Open
aaronpowell wants to merge 1 commit into
aaronpowell-cicd-simplification-stackfrom
cicd/registry-routing
Open

aaronpowell wants to merge 1 commit into
aaronpowell-cicd-simplification-stackfrom
cicd/registry-routing

Conversation

@aaronpowell

@aaronpowell aaronpowell commented Nov 19, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Second layer of the CI/CD simplification stack, based on #14; followed by #16.

  • Use eng/plugins.json for the CI matrix and script selection instead of copied component allowlists and a fixed registry count.
  • Collapse four release callers into one job selected by the existing tag/version/main ancestry plan. Generic *-v* tags fail closed on unknown registry prefixes.
  • Preserve the reusable workflow's per-plugin concurrency, exact artifact promotion, main-only recovery, immutable release/feed comparisons and scoped credentials.
  • Cover registration of a fifth component, duplicate tag-prefix rejection and unknown script selections; retain release destination/recovery regressions.

Validation

All repository/release regression scripts pass, and all workflows pass actionlint. All four components passed local Release, package and loader validation in the cumulative stack. No release script was used to publish anything, and no tags were created.


Stack created with GitHub Stacks CLI

Keep tag/main validation, shared release concurrency and immutable artifact promotion intact while removing copied allowlists and release callers.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@aaronpowell
aaronpowell force-pushed the cicd/registry-routing branch from b97d139 to dfa7ca7 Compare November 20, 2026 03:17
@aaronpowell
aaronpowell marked this pull request as ready for review November 20, 2026 04:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant