Skip to content

ci: register staging-only component metadata repair workflow - #106

Merged
adrianwebb merged 1 commit into
mainfrom
codex/register-component-revision-workflow
Sep 10, 2026
Merged

adrianwebb merged 1 commit into
mainfrom
codex/register-component-revision-workflow

Conversation

@adrianwebb

Copy link
Copy Markdown
Contributor

Outcome

Register the already-verified staging workflow on GitHub's default branch so workflow_dispatch can run it against staging. This is a one-file workflow registration, NOT an application or Identity production promotion.

Work authority

Plan and changes

Copy only .github/workflows/component-revision.yml, byte-for-byte from accepted staging. GitHub returned HTTP404 for dispatch while the workflow was absent from default branch main.

The workflow rejects every ref except current protected staging. It runs the staging metadata-repair tests and appends a new checksum-bound component metadata asset to an existing RC. It preserves source/image identity, does not overwrite assets, rebuild images, publish npm, or alter release tags. The referenced tooling remains on staging and is used only by an explicit staging dispatch.

Verification

Risk and rollback

No application code, credentials, runtime configuration, version, or production inventory changes. Revert this one-file registration if needed; no data migration is performed by merging this PR.

Completion

Unblocks staging-only repair of Admin rc35 metadata, needed before the shared PostgreSQL/Identity migration. The host has rolled back safely and health checks pass; the actual Identity plan remains incomplete.

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