Repository navigation
Update framework starters to Fullbleed 0.5.1 - #36
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
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.
The browser, React, Vue, and Next.js starter lockfiles still installed Fullbleed 0.4.1, so new projects missed the released visibility and font-decoration fixes. They now install published 0.5.1 / engine 2.5.24, with unrelated dependencies unchanged.
The editor/download gates retain the four existing layout fixtures and add five released visibility cases plus three underline-thickness variants. PDF text, retained release hashes, and actual decoration stroke widths are checked after browser downloads.
Validation: fresh registry installs and production builds for all four starters; local Chrome editor, source-download, preview, lifecycle and recovery checks; 17 isolated Next.js production-route checks. Retained local results are in
verification/starters-051.json. CI also runs Firefox, WebKit, and React StrictMode. This changes examples and validation only; no package publication is needed.