ci: register staging-only component metadata repair workflow - #106
Merged
Merged
Conversation
This was referenced Sep 10, 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.
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.