Repository navigation
Bump zod and expo in /bwell-react-native - #229
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [zod](https://github.com/colinhacks/zod) to 4.6.7 and updates ancestor dependency [expo](https://github.com/expo/expo/tree/HEAD/packages/expo). These dependencies need to be updated together. Updates `zod` from 4.5.4 to 4.6.7 - [Release notes](https://github.com/colinhacks/zod/releases) - [Commits](colinhacks/zod@v4.5.4...v4.6.7) Updates `expo` from 57.0.11 to 58.0.22 - [Release notes](https://github.com/expo/expo/releases) - [Changelog](https://github.com/expo/expo/blob/expo@58.0.22/packages/expo/CHANGELOG.md) - [Commits](https://github.com/expo/expo/commits/expo@58.0.22/packages/expo) --- updated-dependencies: - dependency-name: zod dependency-version: 4.6.7 dependency-type: indirect - dependency-name: expo dependency-version: 58.0.22 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
| "@react-navigation/native": "^7.1.6", | ||
| "@tanstack/react-query": "^5.81.5", | ||
| "expo": "~57.0.11", | ||
| "expo": "~58.0.22", |
There was a problem hiding this comment.
🔴 After merging, the app runs Expo SDK 58 alongside SDK 57 modules. Installs carry two different versions of expo-constants and expo-font, and native builds can fail or crash. Only expo moved to ~58.0.22. Every other expo-* range stays on ~57, and so does eslint-config-expo. Fix: run npx expo install --fix (or move the whole bump to SDK 58) so all SDK packages match. That includes expo-router, expo-constants, expo-font and eslint-config-expo, plus the react-native/react versions SDK 58 expects. Then regenerate the lockfile so there is one copy of each module.
Why this was flagged
expo is ~58.0.22 at bwell-react-native/package.json:21. Lines 22-33 keep expo-blur, expo-constants, expo-font, expo-router and others on ~57.x. The regenerated lockfile shows the split. node_modules/expo-constants is 57.0.17 (package-lock.json:7719), while node_modules/expo/node_modules/expo-constants is 58.0.14 (:8351). node_modules/expo-font is 57.0.3 (:7742), while node_modules/expo/node_modules/expo-font is 58.0.11 (:8365). expo-modules-core 58.0.29 exists only nested under expo (:8376). @ expo/config-plugins is 57.0.9 at root (:1910) and 58.0.11 nested (:8236). Autolinking and Metro can then register or bundle two versions of the same native module, or build SDK 57 module code against SDK 58 core. The result is native build failures, duplicate-module errors or runtime crashes in the example app. On the base branch every Expo package was on one SDK (57). The peer ranges "expo": "*" in the 57.x packages hide the mismatch from npm, so npm install raises no warning.
Verification: Trigger: any fresh npm ci or native build of the merged app. In bwell-react-native/package.json the diff changes only "expo": "~57.0.11" to "expo": "~58.0.22" (line 21). Every other SDK package stays on 57. So the install has two versions of the expo-constants and expo-font native modules. On the base, everything was consistently on 57.
Bumps zod to 4.6.7 and updates ancestor dependency expo. These dependencies need to be updated together.
Updates
zodfrom 4.5.4 to 4.6.7Release notes
Sourced from zod's releases.
... (truncated)
Commits
b500a2e4.6.79c21983ci: stage at verbose so a failed OIDC token exchange says why529f78d4.6.6a0ebf97fix(v4): check array, set and map size bounds before parsing elements (#6652)a2ba4a6fix(types): declare record output and input as members, not base type argumen...c42596brelease: hold the run on the release-approval environment until the staged ve...bacad51docs: square the Code for Japan logo to match the other bronze tiles8fb2fafdocs: crop the Code for Japan logo and list it first in bronzeb2ef983docs: add Code for Japan to bronze sponsors74304cerelease: stage npm versions instead of publishing them (#6622)Updates
expofrom 57.0.11 to 58.0.22Release notes
Sourced from expo's releases.
... (truncated)
Changelog
Sourced from expo's changelog.
... (truncated)
Commits
Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for expo since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.