-
Notifications
You must be signed in to change notification settings - Fork 3
chore: upgrade dev deps #1646
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
Open
cimigree
wants to merge
2
commits into
develop
Choose a base branch
from
chore/upgrade-dev-deps
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
chore: upgrade dev deps #1646
Conversation
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
…hema requirement. Marks certain es lint hooks as warnings instead of failures.
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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.
closes #1624
Dev Dependency Upgrade (January 2026)
This PR updates the development dependencies as part of our 6 month scheduled maintenance.
Used
npm run upgrade-deps:devandexpo-doctor.I also manually bumped key supporting packages (like Expo SDK patch, React Native patch, Jest, TypeScript) and reviewed compatibility with Expo SDK
53.0.25and React Native0.79.6. This quiets the warnings whenever I donpx expo prebuild.Upgraded Packages
All changes were either minor or patch-level, with the exception of two intentional major upgrades (
eslint-plugin-react-hooksanddotenv-cli). All upgrades have been tested locally and in CI.@babel/core@babel/preset-env@babel/runtime@comapeo/cloud@comapeo/schema@eslint/eslintrc@eslint/js@formatjs/cli@tanstack/eslint-plugin-query@turf/distance@types/react@types/semver@wdio/browserstack-service@wdio/globals@wdio/local-runner@wdio/mocha-framework@wdio/spec-reporter@wdio/typesbabel-jestdotenv-clieslinteslint-plugin-jesteslint-plugin-react-hookseslint-plugin-testing-libraryexecaglobalsjestjest-expolint-stagedpatch-packageprettierreact-native-svg-transformersemvertypescripttypescript-eslint(meta)webdriverio+@wdio/*packagesexpo(prod)expo-image(prod)react-native(prod)Packages Not Upgraded
These packages were intentionally held back to avoid premature breaking changes or incompatibilities with Expo SDK 53:
jest-exporeact-test-renderermetro,@react-native/*)@react-navigation/native-stack@react-navigation/native).@testing-library/react-native@react-native-picker/picker,react-native-gesture-handler,react-native-reanimated,react-native-safe-area-context,react-native-screens,react-native-svgexpo doctorrecommends older ones. These are compatible with RN 0.79 and verified working in local and CI builds.@sentry/react-nativefastify@comapeo/core@5.2.1and@comapeo/cloud@0.3.0require Fastify v4. Note: Fastify v4 reached end of support on June 30, 2025 and is no longer receiving security updates. This should be prioritized for upgrade once@comapeo/coresupports Fastify v5.Breaking Changes & Fixes
eslint-plugin-react-hooksv7The upgrade to
eslint-plugin-react-hooks@7.0.1introduced stricter React Hooks rules. Updatedeslint.config.mjsto:set-state-in-effect,purity,incompatible-library,immutability,refs,globals) from errors to warnings to avoid blocking existing code patterns- Is this what we want to do? Or revert the package back to the older version?
@comapeo/schemav2.2.0The
Tracktype'slocationsfield changed fromPosition[]to[Position, Position, ...Position[]](tuple requiring minimum 2 positions). This enforces that tracks must have at least 2 positions to be valid. I don't think we actually have other code or processes for this, so am wondering what else we should do to make sure we have two positions.Validation
All updates were tested locally and on CI:
npm ci,npm run lint,npm test(all 604 tests pass)expo doctorpasses (except for intentionally ignored community registry metadata and intentionally newer packages)npm run test:e2e(Browserstack) runs and passeslint-staged16 confirmed working in pre-commit hook