Skip to content

chore(deps): update dependency react-native-reanimated to v4.5.3 - autoclosed - #306

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/react-native-reanimated-4.x
Closed

chore(deps): update dependency react-native-reanimated to v4.5.3 - autoclosed#306
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/react-native-reanimated-4.x

Conversation

@renovate

@renovate renovate Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
react-native-reanimated (source) 4.2.3 → 4.5.3 age confidence

Release Notes

software-mansion/react-native-reanimated (react-native-reanimated)

v4.5.3: Reanimated - 4.5.3

Compare Source

What's Changed

  • cherry-pick(4.5-stable): Fix crash from withheld exiting layout animations in legacy proxy by @​tomekzaw in #​9984
  • cherry-pick(4.5-stable): Prevent animated views from reverting to stale values after app pause or re-animation by @​tomekzaw in #​9987

Full Changelog: software-mansion/react-native-reanimated@4.5.2...4.5.3

v4.5.2: Reanimated - 4.5.2

Compare Source

What's Changed

Reanimated version supporting Worklets 0.11.

Full Changelog: software-mansion/react-native-reanimated@4.5.1...4.5.2

v4.5.1: Reanimated - 4.5.1

Compare Source

What's Changed

Full Changelog: software-mansion/react-native-reanimated@4.5.0...4.5.1

v4.5.0: Reanimated - 4.5.0

Compare Source

Key changes

More props supported by CSS Core Animation

Shadow (shadowColor, shadowOpacity, shadowRadius, shadowOffset), background, and border (backgroundColor, borderColor, borderWidth, borderRadius) CSS transitions now run on iOS Core Animation.

Using CSS Core Animation required enabling IOS_CSS_CORE_ANIMATION feature flag.

CSS Animations Pseudoselectors

CSS animations now support pseudo-selectors such as :hover, :active, and :focus, with native Apple and Android backends alongside a web implementation.

  • feat: pseudo-selectors web implementation by @​wisniewskij in #​9474
  • feat: CSS Pseudoselectors - android backend by wisniewskij in #​9432
  • feat: CSS Pseudoselectors - apple backend by wisniewskij in #​9297
CSS Animations web support for SVG

Animating react-native-svg components is now available on web.

  • feat: register remaining react-native-svg components for web CSS animations by MatiPl01 in (#​9549)
SharedTransitionBoundary component

Introducing the <SharedTransitionBoundary> component, which scopes shared element transitions to a subtree so only matching elements within the boundary animate together. Useful for isolating shared transitions between screens that would otherwise interfere.

Other changes

New Contributors

Full Changelog: software-mansion/react-native-reanimated@4.4.1...4.5.0

v4.4.3: Reanimated - 4.4.3

Compare Source

What's Changed

  • chore(4.4-stable): align runtime tests with worklets 0.10 behavior by @​MatiPl01 in #​9865
  • cherry-pick(4.4-stable): Fix crash from withheld exiting layout animations in legacy proxy by @​tomekzaw in #​9985
  • cherry-pick(4.4-stable): Prevent animated views from reverting to stale values after app pause or re-animation by @​tomekzaw in #​9988

Full Changelog: software-mansion/react-native-reanimated@4.4.2...4.4.3

v4.4.2: Reanimated - 4.4.2

Compare Source

What's Changed

Android
iOS
All platforms
Types and build

Full Changelog: software-mansion/react-native-reanimated@4.4.1...4.4.2

v4.4.1: Reanimated - 4.4.1

Compare Source

What's Changed

Full Changelog: software-mansion/react-native-reanimated@4.4.0...4.4.1

v4.4.0: Reanimated - 4.4.0

Compare Source

Key changes

iOS CSS Core Animation

Reanimated 4.4.0 introduces a new platform-backed CSS animation engine on iOS that runs animations
directly on Core Animation layers instead of going through the JS-driven update loop. It is hidden
behind the IOS_CSS_CORE_ANIMATION static feature flag.

Animation Backend

A new Animation Backend has been integrated behind a feature flag, which will help greatly with the flow of updating the Shadow Tree in animations.

New useTimestamp hook

A new useTimestamp hook exposes the current frame timestamp as a Shared Value that updates every
frame with the time elapsed since the first frame, with an isActive flag to pause and resume updates.

Precompiled headers on Android

Reanimated's native build on Android now uses precompiled headers (ReanimatedPCH.h), significantly
reducing C++ compile times for both fresh and incremental builds.

Other changes

New Contributors

Full Changelog: software-mansion/react-native-reanimated@4.3.1...4.4.0

v4.3.3: Reanimated - 4.3.3

Compare Source

What's Changed

  • cherry-pick(4.3-stable): prevent animated views from reverting to stale values after app pause or re-animation (#​9527) by @​tomekzaw in #​9971
  • cherry-pick(4.3-stable): Fix crash from withheld exiting layout animations in legacy proxy by @​tomekzaw in #​9976

Full Changelog: software-mansion/react-native-reanimated@4.3.2...4.3.3

v4.3.2: Reanimated - 4.3.2

Compare Source

What's Changed

Android

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot enabled auto-merge (squash) July 28, 2026 17:09
@renovate
renovate Bot force-pushed the renovate/react-native-reanimated-4.x branch 3 times, most recently from e30a034 to ad9a3db Compare July 28, 2026 17:49
GSTJ added a commit that referenced this pull request Jul 28, 2026
@GSTJ
chore(renovate): hold react and the reanimated pair to the Expo SDK line
e0a620a 
react and react-dom were open to bumps the SDK does not sanction. The
workspace is hoisted, so #305's react 19.2.8 for apps/docs alone won the
root node_modules and ran under jest beside the SDK's react-test-renderer
19.2.0, failing three of four suites on the peer assert.

react-native-reanimated, react-native-worklets and react-native-screens
were only held on the example app side. #306 took reanimated 4.5.3 in
packages/modal, which installed a second copy beside the example app's
4.2.3 and asserted on its worklets 0.10.x - 0.11.x peer against the SDK's
0.7.4. Moving worklets up to match fails expo-doctor instead.
@GSTJ GSTJ mentioned this pull request Jul 28, 2026
Merged
@renovate
renovate Bot force-pushed the renovate/react-native-reanimated-4.x branch from ad9a3db to 9cfb385 Compare July 28, 2026 22:17
GSTJ added a commit that referenced this pull request Jul 28, 2026
@GSTJ
chore(renovate): hold react and the reanimated pair to the Expo SDK l…
d1f3353 
…ine (#311)

Two Renovate PRs are red on `react-native-magic-modal#test` for the same
reason: each moves a version the Expo SDK picks. This adds the rules
that stop them being re-proposed. #305 and #306 get closed against it.

## react and react-dom

`renovate.json` already holds react-native, and the shared preset
already disables react-test-renderer on the grounds that react's version
is the SDK's to pick. The preset's Expo rule never lists react or
react-dom though, so they stayed open.

The workspace is hoisted, so whichever react wins the root
`node_modules` is the one packages/modal tests against, whatever any
single package.json says. #305 only edits `apps/docs/package.json`:

```
root  node_modules/react                 19.2.8   <- docs won the root
root  node_modules/react-test-renderer   19.2.0   <- SDK's, unchanged
examples/kitchen-sink/.../react          19.2.0   <- nested, doctor stays quiet
```

@testing-library/react-native asserts the two match, so three of four
suites died before running:

```
Incorrect version of "react-test-renderer" detected.
Expected "19.2.8", but found "19.2.0".
```

react-test-renderer can't follow it up, since the preset disables it.

Holding react costs nothing here. apps/docs is a static export (`next
build`, then `serve out`), and 19.2.1 through 19.2.8 are all Server
Components and Server Actions changes.

## reanimated, worklets and screens

The example-app file rule only reaches
`examples/kitchen-sink/package.json`, so Renovate kept proposing these
on the packages/modal side alone. #306 took reanimated 4.5.3 there,
which installed a second copy beside the example app's 4.2.3 and then
asserted on its own peer:

```
reanimated 4.5.3 peers: react-native-worklets 0.10.x - 0.11.x
expo 55.0.28 ships:     react-native-worklets 0.7.4

[Reanimated] Your installed version of Worklets (0.7.4) is not compatible
with installed version of Reanimated (4.5.3).
```

Moving worklets up to 0.10.3 to satisfy it turns the suites green,
36/36. expo-doctor then fails:

```
X Check that packages match versions required by installed Expo SDK
  package                expected  found
  react-native-worklets  0.7.4     0.10.3
```

Worklets is a native module and isn't on the example app's
`expo.install.exclude` list, only reanimated and gesture-handler are. So
4.5.3 cannot land while the repo is on SDK 55. react-native-screens sits
in the same position and is held for the same reason.

## Verification

Clean `node_modules`, rebased on main:

- oxlint straight from `node_modules/.bin` in all three workspaces, exit
0. Planted an unused var first to confirm it exits 1.
- format, typecheck, build, doctor 19/19, changelog:check all exit 0
- 36 tests across 4 suites
- `renovate-config-validator` accepts the file

Config only, so no E2E and no release.

Proof, including both reproductions and the worklets experiment:
[magic-modal/305-306](https://github.com/GSTJ/pr-assets-dump/tree/magic-modal-305-306-sdk-pins/magic-modal/305-306)

| | |
|---|---|
| [#305
reproduced](https://github.com/GSTJ/pr-assets-dump/blob/magic-modal-305-306-sdk-pins/magic-modal/305-306/305.png)
| [#306
reproduced](https://github.com/GSTJ/pr-assets-dump/blob/magic-modal-305-306-sdk-pins/magic-modal/305-306/306.png)
|
| [worklets aligned, doctor
fails](https://github.com/GSTJ/pr-assets-dump/blob/magic-modal-305-306-sdk-pins/magic-modal/305-306/306-worklets.png)
| [chain green
here](https://github.com/GSTJ/pr-assets-dump/blob/magic-modal-305-306-sdk-pins/magic-modal/305-306/green.png)
|
@renovate renovate Bot changed the title chore(deps): update dependency react-native-reanimated to v4.5.3 chore(deps): update dependency react-native-reanimated to v4.5.3 - autoclosed Jul 28, 2026
@renovate renovate Bot closed this Jul 28, 2026
auto-merge was automatically disabled July 28, 2026 23:07

Pull request was closed

@renovate
renovate Bot deleted the renovate/react-native-reanimated-4.x branch July 28, 2026 23:07
@GSTJ

GSTJ commented Jul 28, 2026

Copy link
Copy Markdown
Owner

Closing. #311 holds reanimated to the Expo SDK line.

4.5.3 in packages/modal installed a second copy beside the example app's 4.2.3, then asserted on its own react-native-worklets: 0.10.x - 0.11.x peer against the SDK's 0.7.4. Moving worklets up to match turns the suites green but fails expo-doctor instead, since worklets is a native module and isn't on the example app's expo.install.exclude list. Moves by hand with the SDK.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@GSTJ