-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update dependency expo to v49.0.8 - autoclosed #11
Conversation
"integrity": "sha512-WFaEWuFEuUpETiq85YlhKYJgedccWTjtCMnYGAgyNfCfvnIgfMCVH7dWudGuxhfAcTZqh36OcqtSckbtbhOtyg==", | ||
"version": "15.4.3", | ||
"resolved": "https://registry.npmjs.org/expo-file-system/-/expo-file-system-15.4.3.tgz", | ||
"integrity": "sha512-HaaCBTUATs2+i7T4jxIvoU9rViAHMvOD2eBaJ1H7xPHlwZlMORjQs7bsNKonR/TQoduxZBJLVZGawvaAJNCH8g==", | ||
"dependencies": { | ||
"uuid": "^3.4.0" | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pull request seems to update the version numbers and integrity hashes of the dependencies in the package.json file. It looks good, but I would suggest adding a brief explanation or reasoning for any significant changes made in the commit message.👍
570f5d4
to
748a2a4
Compare
"integrity": "sha512-kQxllZfus7wM0O6X0Ud+SOnbH/kbxtEAQp2gkvDq3P3kqhtafue/H9CPDX04uWc/pypvp9vp/sZ+qvA0alaVuQ==", | ||
"version": "1.5.10", | ||
"resolved": "https://registry.npmjs.org/expo-modules-core/-/expo-modules-core-1.5.10.tgz", | ||
"integrity": "sha512-+m+poHkhjAhRZmngSLUpJJoxhjoExYKSr4J5luy4N+YMlowK31Zewztg4xsPrNRoPvGK/B5uCm0UEzIQvLsNGg==", | ||
"dependencies": { | ||
"compare-versions": "^3.4.0", | ||
"invariant": "^2.2.4" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pull request seems to update various dependencies including "@babel/core", "babel-preset-expo", "expo-file-system", "expo-modules-autolinking" and "expo-modules-core". All the changes look good. However, it is suggested to provide a reason behind these updates in the pull request description for better clarity. Additionally, emojis could be added to the feedback to make it more engaging.
748a2a4
to
4d2d881
Compare
"integrity": "sha512-kQxllZfus7wM0O6X0Ud+SOnbH/kbxtEAQp2gkvDq3P3kqhtafue/H9CPDX04uWc/pypvp9vp/sZ+qvA0alaVuQ==", | ||
"version": "1.5.10", | ||
"resolved": "https://registry.npmjs.org/expo-modules-core/-/expo-modules-core-1.5.10.tgz", | ||
"integrity": "sha512-+m+poHkhjAhRZmngSLUpJJoxhjoExYKSr4J5luy4N+YMlowK31Zewztg4xsPrNRoPvGK/B5uCm0UEzIQvLsNGg==", | ||
"dependencies": { | ||
"compare-versions": "^3.4.0", | ||
"invariant": "^2.2.4" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes seem to be updating the versions of several packages, including babel-preset-expo
, its peer dependency metro-react-native-babel-preset
, and expo-filesystem
. There do not seem to be any immediate issues with the changes and they appear to be routine updates.
If this is a public repository, it would be helpful to include information about what prompted these changes (e.g., bug fix, new feature, version compatibility), as well as update the relevant documentation or README file accordingly.
This PR contains the following updates:
49.0.6
->49.0.8
Release Notes
expo/expo (expo)
v49.0.8
Compare Source
v49.0.7
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.