Repository navigation
Restore check-generated extension metadata from exact CI source - #80
Merged
callumalpass merged 1 commit intoOct 20, 2026
Merged
Conversation
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
1 participant
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.
Parent direct approval of qualified R9 eb6ee21/treeab79352e39f79e9cc79b647badbc9535874f01ae. Actual535 run39411577193 passed frozen originals and full check, then refused its first pre-build clean-source guard because default-LAB checks had regenerated the tracked production extension manifest. No app compilation/upload occurred.
Minimal remedy: after successful pnpm check in ephemeral CI only, copy exactly apps/extension/src/generated/mdbase-app.json from validated SOURCE_SHA using literal git show. Existing clean-source guard remains unchanged and other dirty paths still refuse. Actual target build must regenerate correct staging metadata with approved key/ID. One existing-suite causal regression, no helper/guard/framework. Two files +60/-1, only two workflow lines. Key scope/page20/original byte/SRI/lock/member/artifact/upload checks unchanged.
Baseline actual-message RED172 pass/1 fail, then full supported check PASS: publisher173, Reader450+39, extension187, Connect167, types/lint/format/architecture and actionlint. No product build/repack. Source qualifications and historical f5 products remain separate from actual535 failure.
Source PR ONLY to release/native-staging; Parent R13 authorizes normal SHA-bound merge and ONE necessary fixed-source Stage publisher. No main/production authority.