Repository navigation
fix(release): preserve qualified Frame through documentation updates - #374
Merged
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
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.
The beta.2 tag preflight rejected approved documentation and the native-client Beta description after the qualified Frame build. Allow the six specific documentation/image paths, and allow built AppStream metadata only when its bytes equal the single
This Alpha targets→This Beta targetsreplacement in a regular 0644 blob. Other metadata, runtime edits and near-name paths still refuse before release calls.Frame source, bundle/runtime pins, asset checks, curated notes and publication behavior are unchanged. This changes only the release workflow and its existing metadata regression test.
Validation: the original guard fails the new regression; the correction passes all 37 fixture cases (14 positive variants, 23 expected refusals), the actual source-history identity check, public-docs/surface checks, and independent exact-source review. The first fixture failure is retained; it was corrected by staging only intended fixture paths. Normal required source CI is qualified separately before integration. Existing runtime and device evidence carries because those inputs are unchanged.