chore(deps): bump expo-constants from 17.0.8 to 17.1.8#45
Conversation
c6737f4 to
aed0ab2
Compare
Bumps [expo-constants](https://github.com/expo/expo/tree/HEAD/packages/expo-constants) from 17.0.8 to 17.1.8. - [Changelog](https://github.com/expo/expo/blob/main/packages/expo-constants/CHANGELOG.md) - [Commits](https://github.com/expo/expo/commits/HEAD/packages/expo-constants) --- updated-dependencies: - dependency-name: expo-constants dependency-version: 17.1.8 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
aed0ab2 to
7b28aae
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7b28aae093
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "@quanux/ui": "workspace:*", | ||
| "expo": "~52.0.48", | ||
| "expo-constants": "~17.0.8", | ||
| "expo-constants": "~17.1.8", |
There was a problem hiding this comment.
Keep expo-constants aligned with Expo SDK 52
Bumping expo-constants to ~17.1.8 here puts the React Native apps out of sync with the rest of the SDK 52 dependency graph: expo-router@4.0.22 still declares expo-constants: ~17.0.8 (pnpm-lock.yaml line 5110) and expo@52.0.48 still pulls expo-constants@17.0.8 (pnpm-lock.yaml line 13875). That creates a mixed/unsupported Expo module set (17.0.8 and 17.1.8 together), which is prone to Expo dependency-check failures and runtime native-module incompatibilities across mobile targets.
Useful? React with 👍 / 👎.
Bumps expo-constants from 17.0.8 to 17.1.8.
Changelog
Sourced from expo-constants's changelog.
... (truncated)
Commits
Maintainer changes
This version was pushed to npm by alanhughes, a new releaser for expo-constants 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)