chore(deps): bump react family, framer-motion, ws and @modelcontextprotocol/sdk - #108
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Aug 26, 2026
This branch was successfully deployed
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.
Second dependabot round, opened after #100 and #101 landed. Batches five of the six new PRs;
changesets/action(#102) is deliberately left out — see below.69a94c645a5f70a5fe9429456c9511cd51aOn the framer-motion major
13.0.0 has exactly one breaking change: the optional
@emotion/is-prop-validdependency was removed in favour of an explicit<MotionConfig isValidProp={isPropValid}>. This repo has no@emotion/*, nostyled-components, and noMotionConfigusage, so nothing is affected. The 27framer-motionimports acrossapps/webandpackages/generatorusemotion,animate,useReducedMotion,AnimatePresence,useInView,useScroll,useTransform,useSpringandReorder— all unchanged. 13.1.0'sReorderadditions are additive.On the react grouping
react (#103) and react-dom (#107) arrived as separate PRs — the same lockstep problem the
playwrightgroup exists to prevent. They are one runtime split across two packages, and the@types/*must describe the version actually installed. Added areactgroup, plus the matchingexclude-patternsondev-dependenciesso the@types/*packages do not get claimed away from it (the exact failure mode that produced the #94/#99 skew).Why #102 is not here
changesets/actionv1 → v2 is a breaking change this workflow is not ready for. v2 requires the token to be passed as an explicitgithub-tokeninput — theGITHUB_TOKENenvironment variable and the credentials configured byactions/checkoutare no longer accepted..github/workflows/release.ymlcurrently passes it only viaenv: GITHUB_TOKEN, so merging #102 as-is would break the release pipeline, and the failure would only surface at publish time. It needs a companion edit, not a plain bump.Verification
Same steps as CI, locally:
pnpm install --frozen-lockfile,lint(0),typecheck(10/10),test(9/9),build(7/7),check:exports(13/13).