Skip to content

Comments

[pull] main from motiondivision:main#212

Merged
pull[bot] merged 4 commits intocode:mainfrom
motiondivision:main
Feb 6, 2026
Merged

[pull] main from motiondivision:main#212
pull[bot] merged 4 commits intocode:mainfrom
motiondivision:main

Conversation

@pull
Copy link

@pull pull bot commented Feb 6, 2026

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

mattgperry and others added 4 commits February 6, 2026 10:48
In SPA frameworks, page navigation removes DOM elements externally
without going through Motion's projection unmount path. This left
zombie projection nodes in the NodeStack, causing broken layout
animations when new elements with the same layoutId mounted.

Guard against stale nodes in three places:
- promote(): skip setting resumeFrom when prevLead has a disconnected
  instance and no snapshot (zombie from external removal)
- relegate(): skip disconnected candidates when finding a new lead
- add(): prune zombie members (but preserve lead/prevLead for the
  current animation cycle)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Bumps [next](https://github.com/vercel/next.js) from 15.4.10 to 15.5.10.
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v15.4.10...v15.5.10)

---
updated-dependencies:
- dependency-name: next
  dependency-version: 15.5.10
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
Fix stale shared layout nodes during SPA navigations
…next-15.5.10

chore(deps): bump next from 15.4.10 to 15.5.10
@pull pull bot locked and limited conversation to collaborators Feb 6, 2026
@pull pull bot added the ⤵️ pull label Feb 6, 2026
@pull pull bot merged commit c78c52d into code:main Feb 6, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant