Repository navigation
Document the 2.5.15 border-image follow-up - #79
Merged
Merged
Conversation
krflol
marked this pull request as ready for review
October 8, 2026 02:30
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 corpus guide's border-image example now has a later fix. Link the retained 2.5.14 baseline to the 2.5.15 follow-up, explain the source-candidate comparison, and provide the evidence and reproduction links. Keep the original counts, images and failure list intact.
Validation: strict MkDocs build, the 78-page internal link/anchor audit, and desktop/mobile browser checks pass. The 390px and 1440px previews retain both result sets with no horizontal overflow or page errors. The Rust verification feature,
svg_raster, is explicit.The 2.5.15 release is published. Fresh public Python and Rust consumers passed all 21 focused cases, both bundled reproduction commands passed, and all six release downloads were fetched anonymously and checked against their SHA-256 hashes.