Repository navigation
test(SkeletonMode): pin the cross-version gate to 1.5.0-next.31 - #3413
Merged
Merged
Conversation
1.5.0-next.31 is the first published version with SkeletonMode (#3317 merged right before it). The gate at 1.5.0-next.27 let the harness compare next.27 to next.30, which lack the component. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
✅ Cross-Version Tests PassedThe current host still renders old published remote versions correctly (iframe) and in the same DOM shape (in-process). Iframe harness (attribute-accurate): ✅ passed In-process harness (structure-only): ✅ passed |
Contributor
🚀 Preview DeploymentPreview environments are ready:
Images:
|
Lisa18289
approved these changes
Oct 8, 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.
Pins
skeletonModeSinceto1.5.0-next.31, the first published version that containsSkeletonMode(#3317 merged at 07:40,next.31was published at 07:45). The old value1.5.0-next.27was a placeholder from before the merge, so the cross-version harness would comparenext.27–next.30, which lack the component and fail with "Element type is invalid".Checked with
npm pack @mittwald/flow-react-components@<v> --dry-run:next.30has no SkeletonMode,next.31andnext.32have it.Tests only, no release.
🤖 Generated with Claude Code