Repository navigation
chore: integration check for the follow-up stack (do not merge) - #339
Closed
leoafarias wants to merge 1 commit into
Closed
leoafarias wants to merge 1 commit into
leoafarias wants to merge 1 commit into
Conversation
This was referenced Oct 27, 2026
Closed
leoafarias
force-pushed
the
stack/follow-ups-integration
branch
from
October 29, 2026 21:44
c931a3a to
d5990f4
Compare
Collaborator
Author
|
Superseded by #360, which carries these changes. Closing; the branch is kept. |
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.
Integration only — DO NOT MERGE. The owning PRs remain the merge/release units. This PR remains a draft.
Refreshes the follow-up integration snapshot onto main
ca9331beafter squash-merge #321. Its two old commits are absent from the rebuilt history. The rebuild uses one linear integration commit; it creates no Git merge commits.Includes current runtime/registry owning changes from #317, #318, #319, #320, #322, #323, #324, #325, #326, #327, #328, #329, #330, #331, #332, #333, #334, #335, #337, #338, #340, #341, #344, #345, #347, #348, #349, #350, and the split Remix slider draft #352. The new #334 and #352 slider source/test blobs match their owner heads exactly.
Stacks preserved: #320 → #328; #335 → #337; #347 → #341 → #345 → #348. #348 inherits #347's API without duplicate Naked UI commits. #342/#343/#346 are adoption drafts above this hub, blocked on published naked_ui 1.3.0 and Remix 1.0.0-beta.14 and approved floor updates. No release or registry-floor change is part of this refresh.
The runtime tree preserves Hero's prior conflict resolutions, including the accordion reduced-motion regression, the select arrow counts (8→7, 20→19, 11→12), combined effect/state scopes, all CHANGELOG entries, and generated HeroUI radio/switch adapters. The refresh only formats the combined consumer checker; it does not invent new regression fixes. Deferred ADR/AGENTS consolidation and the held HeroUI ADR rewrite are not applied.
Validated with pinned Flutter 3.44.0:
melos run ci:checks: passes, including docs and registry derivation checks.git merge-tree; its ownership preflight and test(registry): amortize checkout CLI startup #351 compiled-consumer path are both retained.GitHub Checks validate this refreshed integration head separately. This PR remains DO NOT MERGE regardless of its check state.
Open workspace in Conductor