chore(deps): update all non-major dependencies#1248
chore(deps): update all non-major dependencies#1248renovate[bot] wants to merge 1 commit intomainfrom
Conversation
|
More templates
@tanstack/angular-db
@tanstack/db
@tanstack/db-ivm
@tanstack/electric-db-collection
@tanstack/offline-transactions
@tanstack/powersync-db-collection
@tanstack/query-db-collection
@tanstack/react-db
@tanstack/rxdb-db-collection
@tanstack/solid-db
@tanstack/svelte-db
@tanstack/trailbase-db-collection
@tanstack/vue-db
commit: |
|
Size Change: 0 B Total Size: 92 kB ℹ️ View Unchanged
|
|
Size Change: 0 B Total Size: 3.7 kB ℹ️ View Unchanged
|
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
25 times, most recently
from
8ea5edb to
1f2a1a9
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
24 times, most recently
from
74558e5 to
fc33278
Compare
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughBumped GitHub Actions checkout pins and other workflow action versions, updated pnpm/toolchain, upgraded numerous dependency and devDependency versions across root, packages, and example manifests, and updated a Gradle wrapper in a React Native example. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
📝 Coding Plan
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@examples/react/projects/package.json`:
- Around line 27-28: The package has a version mismatch between the tRPC
packages: `@trpc/client` is ^11.12.0 while `@trpc/server` is ^11.10.0; update the
dependency versions so both `@trpc/client` and `@trpc/server` use the same
compatible version (e.g., set `@trpc/server` to ^11.12.0 or pin both to the same
exact version) in package.json to keep client/server parity and avoid subtle
incompatibilities.
- Line 37: Remove the runtime dependency entry for "vite" from the package.json
"dependencies" section (the duplicate "vite": "^7.3.0" entry) and ensure "vite"
remains only in "devDependencies" (use the desired version, e.g., "^7.3.1"
already present); update the dependencies block to delete the "vite" key so
build tooling is not bundled into production installs and verify
package-lock/yarn.lock is updated after installing to reflect the change.
In `@packages/offline-transactions/package.json`:
- Around line 77-80: Replace the deprecated NativeEventSubscription type with
the public EventSubscription in ReactNativeOnlineDetector.ts: change the import
to bring in EventSubscription (keeping AppStateStatus) and update the
subscription variable/type declaration (the variable currently typed as
NativeEventSubscription | null) to EventSubscription | null so typings match RN
>=0.80 while leaving the existing .remove() unsubscribe logic intact.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: c65fef04-ff40-47db-8cf9-b9a260ecf8ea
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (29)
.github/workflows/autofix.yml.github/workflows/claude.yml.github/workflows/e2e-tests.yml.github/workflows/pr.yml.github/workflows/release.yml.github/workflows/reproduce-and-fix-issue-claude.yml.github/workflows/review-pr-claude.yml.tool-versionsexamples/angular/todos/package.jsonexamples/react-native/offline-transactions/android/gradle/wrapper/gradle-wrapper.propertiesexamples/react-native/offline-transactions/package.jsonexamples/react/offline-transactions/package.jsonexamples/react/paced-mutations-demo/package.jsonexamples/react/projects/package.jsonexamples/react/todo/package.jsonexamples/solid/todo/package.jsonpackage.jsonpackages/angular-db/package.jsonpackages/db-collection-e2e/package.jsonpackages/db/package.jsonpackages/electric-db-collection/package.jsonpackages/offline-transactions/package.jsonpackages/powersync-db-collection/package.jsonpackages/react-db/package.jsonpackages/rxdb-db-collection/package.jsonpackages/solid-db/package.jsonpackages/svelte-db/package.jsonpackages/trailbase-db-collection/package.jsonpackages/vue-db/package.json
| "@trpc/client": "^11.12.0", | ||
| "@trpc/server": "^11.10.0", |
There was a problem hiding this comment.
Version mismatch between @trpc/client and @trpc/server.
@trpc/client is updated to ^11.12.0 while @trpc/server remains at ^11.10.0. While tRPC generally maintains compatibility within minor versions, keeping client and server versions aligned is recommended to avoid subtle incompatibilities.
🔧 Proposed fix to align tRPC versions
"@trpc/client": "^11.12.0",
- "@trpc/server": "^11.10.0",
+ "@trpc/server": "^11.12.0",📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "@trpc/client": "^11.12.0", | |
| "@trpc/server": "^11.10.0", | |
| "@trpc/client": "^11.12.0", | |
| "@trpc/server": "^11.12.0", |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@examples/react/projects/package.json` around lines 27 - 28, The package has a
version mismatch between the tRPC packages: `@trpc/client` is ^11.12.0 while
`@trpc/server` is ^11.10.0; update the dependency versions so both `@trpc/client`
and `@trpc/server` use the same compatible version (e.g., set `@trpc/server` to
^11.12.0 or pin both to the same exact version) in package.json to keep
client/server parity and avoid subtle incompatibilities.
| "@react-native-community/netinfo": "11.5.2", | ||
| "@types/node": "^25.2.2", | ||
| "eslint": "^9.39.2", | ||
| "react-native": "0.79.6", | ||
| "eslint": "^9.39.4", | ||
| "react-native": "0.84.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check for React Native specific code that might be affected by the version bump
echo "=== React Native specific exports and code ==="
fd -t f -e ts -e tsx . packages/offline-transactions/src --exec grep -l "react-native" {} \;
echo ""
echo "=== Checking for RN-specific APIs used ==="
rg -n "from ['\"]react-native['\"]" packages/offline-transactions/src/ || echo "No direct react-native imports found"
echo ""
echo "=== Checking netinfo usage ==="
rg -n "@react-native-community/netinfo" packages/offline-transactions/src/ || echo "No netinfo imports found"Repository: TanStack/db
Length of output: 850
🏁 Script executed:
cat -n packages/offline-transactions/src/connectivity/ReactNativeOnlineDetector.tsRepository: TanStack/db
Length of output: 4045
🏁 Script executed:
cat -n packages/offline-transactions/src/types.ts | head -100Repository: TanStack/db
Length of output: 3105
🌐 Web query:
React Native 0.84 0.79 breaking changes AppState NativeEventSubscription
💡 Result:
Between React Native 0.79 → 0.84, the “breaking” part you’re likely hitting around AppState + NativeEventSubscription is event subscription typing/imports, due to RN’s push to a stable public JS API:
- Deep imports were deprecated in RN 0.80 and targeted for removal in 0.82+. So any code importing
NativeEventSubscriptionfrom internal paths likereact-native/Libraries/...can break by the time you’re on 0.84. Use root imports fromreact-nativeinstead. [1] AppState.addEventListener(...)returns a subscription object with.remove()(RN docs show the method returning aNativeEventSubscription, while also describing it as anEventSubscription). Treat it as an “event subscription” and call.remove()to unsubscribe. [2]- In newer docs/guides, RN standardizes on the
EventSubscriptiontype imported fromreact-native(instead of referencing internalNativeEventSubscriptiontypes). [3]
Practical fix (TS-friendly):
- Replace deep imports of
NativeEventSubscriptionwith either:import type { EventSubscription } from 'react-native';, ortype Sub = ReturnType<typeof AppState.addEventListener>;(avoids depending on a specific exported type name)
- Unsubscribe with
subscription.remove().
Sources: React Native “Moving Towards a Stable JavaScript API” (0.80) [1], AppState docs (shows NativeEventSubscription return and “Returns the EventSubscription”) [2], New Architecture events docs (uses EventSubscription from react-native) [3].
Use EventSubscription type instead of deprecated NativeEventSubscription.
The react-native version jump to 0.84.1 introduces a typing concern: NativeEventSubscription is deprecated in favor of the public EventSubscription type (available since RN 0.80).
In packages/offline-transactions/src/connectivity/ReactNativeOnlineDetector.ts (line 3), replace:
import type { AppStateStatus, NativeEventSubscription } from 'react-native'with:
import type { AppStateStatus, EventSubscription } from 'react-native'Then update line 15 to use EventSubscription | null instead of NativeEventSubscription | null. The runtime behavior (using .remove() to unsubscribe) is already correct and compatible.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/offline-transactions/package.json` around lines 77 - 80, Replace the
deprecated NativeEventSubscription type with the public EventSubscription in
ReactNativeOnlineDetector.ts: change the import to bring in EventSubscription
(keeping AppStateStatus) and update the subscription variable/type declaration
(the variable currently typed as NativeEventSubscription | null) to
EventSubscription | null so typings match RN >=0.80 while leaving the existing
.remove() unsubscribe logic intact.
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
.github/workflows/reproduce-and-fix-issue-claude.yml (1)
31-31: Pinactions/checkoutto a full commit SHA.GitHub documents full-length commit SHAs as the only immutable action reference, and repository policies can require SHA-pinned actions. Since this workflow has
contents: writeandid-token: write, use the SHA directly instead of a mutable tag.Replace
v6.0.2withde0fac2e4500dabe0009e67214ff5f5447ce83dd:uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/workflows/reproduce-and-fix-issue-claude.yml at line 31, The workflow is pinning actions/checkout to a mutable tag (uses: actions/checkout@v6.0.2); replace that tag with the full commit SHA to make the action reference immutable (uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd). Update the single line containing "uses: actions/checkout@v6.0.2" to use the provided SHA, confirm the workflow still passes, and commit the change..github/workflows/claude.yml (1)
21-21: Pin this checkout step to a full commit SHA for immutability hardening.
v6.0.2is a mutable tag. GitHub recommends using full commit SHAs for immutable action references, which can be enforced repo-wide via policy (GitHub security guide).Change
uses: actions/checkout@v6.0.2touses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/workflows/claude.yml at line 21, Replace the mutable tag reference "actions/checkout@v6.0.2" with the provided full commit SHA "actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd" to pin the checkout action immutably; locate the uses: actions/checkout entry in the workflow and update the version string to the SHA to ensure reproducible/immutable action resolution.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@packages/rxdb-db-collection/package.json`:
- Line 67: Search for all usages of the removed 0.8 constructor API "new
Store(...)" (e.g., the spots flagged in the review where the store is
instantiated) and replace each with a call to createStore(...) from
`@tanstack/store`; update the import to import { createStore } from
'@tanstack/store' and remove any imports of Store. After replacing
instantiations, run a quick grep for symbols Removed in 0.9 such as "Derived"
and "Effect" and remove/replace them with the 0.9 equivalents or refactor to the
new reactive primitives so no references to the removed 0.8 APIs remain. Ensure
the new createStore usage matches the 0.9 call signature used elsewhere in the
repo and run tests/build to confirm no remaining incompatibilities.
---
Nitpick comments:
In @.github/workflows/claude.yml:
- Line 21: Replace the mutable tag reference "actions/checkout@v6.0.2" with the
provided full commit SHA
"actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd" to pin the checkout
action immutably; locate the uses: actions/checkout entry in the workflow and
update the version string to the SHA to ensure reproducible/immutable action
resolution.
In @.github/workflows/reproduce-and-fix-issue-claude.yml:
- Line 31: The workflow is pinning actions/checkout to a mutable tag (uses:
actions/checkout@v6.0.2); replace that tag with the full commit SHA to make the
action reference immutable (uses:
actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd). Update the single
line containing "uses: actions/checkout@v6.0.2" to use the provided SHA, confirm
the workflow still passes, and commit the change.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 282d321e-576d-40f5-8811-934999527422
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (29)
.github/workflows/autofix.yml.github/workflows/claude.yml.github/workflows/e2e-tests.yml.github/workflows/pr.yml.github/workflows/release.yml.github/workflows/reproduce-and-fix-issue-claude.yml.github/workflows/review-pr-claude.yml.tool-versionsexamples/angular/todos/package.jsonexamples/react-native/offline-transactions/android/gradle/wrapper/gradle-wrapper.propertiesexamples/react-native/offline-transactions/package.jsonexamples/react/offline-transactions/package.jsonexamples/react/paced-mutations-demo/package.jsonexamples/react/projects/package.jsonexamples/react/todo/package.jsonexamples/solid/todo/package.jsonpackage.jsonpackages/angular-db/package.jsonpackages/db-collection-e2e/package.jsonpackages/db/package.jsonpackages/electric-db-collection/package.jsonpackages/offline-transactions/package.jsonpackages/powersync-db-collection/package.jsonpackages/react-db/package.jsonpackages/rxdb-db-collection/package.jsonpackages/solid-db/package.jsonpackages/svelte-db/package.jsonpackages/trailbase-db-collection/package.jsonpackages/vue-db/package.json
🚧 Files skipped from review as they are similar to previous changes (22)
- .github/workflows/pr.yml
- packages/svelte-db/package.json
- packages/trailbase-db-collection/package.json
- examples/react/offline-transactions/package.json
- packages/offline-transactions/package.json
- .github/workflows/review-pr-claude.yml
- examples/react/paced-mutations-demo/package.json
- packages/db/package.json
- packages/db-collection-e2e/package.json
- packages/powersync-db-collection/package.json
- packages/vue-db/package.json
- packages/react-db/package.json
- examples/angular/todos/package.json
- .github/workflows/release.yml
- examples/solid/todo/package.json
- .github/workflows/e2e-tests.yml
- .github/workflows/autofix.yml
- packages/angular-db/package.json
- examples/react/todo/package.json
- examples/react/projects/package.json
- examples/react-native/offline-transactions/package.json
- examples/react-native/offline-transactions/android/gradle/wrapper/gradle-wrapper.properties
| "@standard-schema/spec": "^1.1.0", | ||
| "@tanstack/db": "workspace:*", | ||
| "@tanstack/store": "^0.8.0", | ||
| "@tanstack/store": "^0.9.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
rg -n -C2 -g '*.ts' -g '*.tsx' -g '*.js' -g '*.jsx' 'new\s+(Store|Derived|Effect)\s*\(' packages
rg -n -C2 -g '*.ts' -g '*.tsx' -g '*.js' -g '*.jsx' '@tanstack/store' packagesRepository: TanStack/db
Length of output: 1240
🏁 Script executed:
#!/bin/bash
# Check if other packages have `@tanstack/store` in their package.json
fd -t f 'package.json' packages | while read pf; do
if grep -q '@tanstack/store' "$pf" 2>/dev/null; then
echo "=== $pf ==="
grep '@tanstack/store' "$pf"
fi
done
# Get more context around the new Store() usage
echo -e "\n=== Context around new Store() in trailbase.ts ==="
sed -n '125,135p' packages/trailbase-db-collection/src/trailbase.ts
# Check for any Store instantiation patterns in electric-db-collection
echo -e "\n=== Searching electric-db-collection for Store usage ==="
rg -n 'new\s+Store|createStore' packages/electric-db-collection/srcRepository: TanStack/db
Length of output: 1496
Migrate to @tanstack/store@0.9 API before merging — code is currently incompatible with the package.json constraint.
The package.json files across all collections have been updated to @tanstack/store@0.9.2, but the source code still uses the old 0.8.x constructor API (new Store(...)) which was removed in 0.9.0. Found new Store() usages in:
packages/trailbase-db-collection/src/trailbase.ts:128packages/electric-db-collection/src/electric.ts:571, 572, 576, 590, 594, 938
Replace all new Store(...) with createStore(...) and verify there are no remaining usages of removed 0.8 APIs (Derived, Effect).
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/rxdb-db-collection/package.json` at line 67, Search for all usages
of the removed 0.8 constructor API "new Store(...)" (e.g., the spots flagged in
the review where the store is instantiated) and replace each with a call to
createStore(...) from `@tanstack/store`; update the import to import { createStore
} from '@tanstack/store' and remove any imports of Store. After replacing
instantiations, run a quick grep for symbols Removed in 0.9 such as "Derived"
and "Effect" and remove/replace them with the 0.9 equivalents or refactor to the
new reactive primitives so no references to the removed 0.8 APIs remain. Ensure
the new createStore usage matches the 0.9 call signature used elsewhere in the
repo and run tests/build to confirm no remaining incompatibilities.
There was a problem hiding this comment.
🧹 Nitpick comments (1)
examples/angular/todos/package.json (1)
38-40: Align@angular/compiler-clito match@angular/cliand@angular/buildversions.The package.json shows
@angular/cliand@angular/buildat20.3.20, while@angular/compiler-cliremains at20.3.18. Although patch-level mismatches within the same minor line typically work, Angular's coordinated release model packages these tools together. Aligning@angular/compiler-clito20.3.20ensures consistency with Angular's build toolchain expectations and avoids potential edge-case compatibility issues.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@examples/angular/todos/package.json` around lines 38 - 40, Update the `@angular/compiler-cli` dependency version to match the other Angular toolchain entries by changing "@angular/compiler-cli" from "20.3.18" to "20.3.20" in package.json so it aligns with "@angular/cli" and "@angular/build" and avoids toolchain version mismatch issues.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@examples/angular/todos/package.json`:
- Around line 38-40: Update the `@angular/compiler-cli` dependency version to
match the other Angular toolchain entries by changing "@angular/compiler-cli"
from "20.3.18" to "20.3.20" in package.json so it aligns with "@angular/cli" and
"@angular/build" and avoids toolchain version mismatch issues.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 9bf04172-f46a-4809-8984-86f270793cf5
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (29)
.github/workflows/autofix.yml.github/workflows/claude.yml.github/workflows/e2e-tests.yml.github/workflows/pr.yml.github/workflows/release.yml.github/workflows/reproduce-and-fix-issue-claude.yml.github/workflows/review-pr-claude.yml.tool-versionsexamples/angular/todos/package.jsonexamples/react-native/offline-transactions/android/gradle/wrapper/gradle-wrapper.propertiesexamples/react-native/offline-transactions/package.jsonexamples/react/offline-transactions/package.jsonexamples/react/paced-mutations-demo/package.jsonexamples/react/projects/package.jsonexamples/react/todo/package.jsonexamples/solid/todo/package.jsonpackage.jsonpackages/angular-db/package.jsonpackages/db-collection-e2e/package.jsonpackages/db/package.jsonpackages/electric-db-collection/package.jsonpackages/offline-transactions/package.jsonpackages/powersync-db-collection/package.jsonpackages/react-db/package.jsonpackages/rxdb-db-collection/package.jsonpackages/solid-db/package.jsonpackages/svelte-db/package.jsonpackages/trailbase-db-collection/package.jsonpackages/vue-db/package.json
🚧 Files skipped from review as they are similar to previous changes (15)
- examples/react/paced-mutations-demo/package.json
- packages/svelte-db/package.json
- packages/db/package.json
- examples/react/offline-transactions/package.json
- package.json
- packages/powersync-db-collection/package.json
- packages/angular-db/package.json
- .github/workflows/pr.yml
- .tool-versions
- packages/db-collection-e2e/package.json
- packages/vue-db/package.json
- examples/react/projects/package.json
- packages/solid-db/package.json
- .github/workflows/claude.yml
- packages/rxdb-db-collection/package.json
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@examples/react-native/offline-transactions/package.json`:
- Around line 21-28: Update the package.json dependency versions for
react-native and metro to Expo SDK 53-compatible releases: change "react-native"
from 0.84.1 to a 0.79.x version and "metro" from 0.84.2 to 0.82.x so they match
Expo SDK 53 (e.g., react-native 0.79.x and metro 0.82.x); ensure you update any
lockfile (yarn.lock or package-lock.json) and reinstall dependencies so the
managed workflow uses the supported RN/Metro pair.
In `@examples/react/todo/package.json`:
- Around line 40-42: Update the eslint-plugin-react-hooks dependency in
package.json: replace the current "eslint-plugin-react-hooks": "^5.2.0" entry
with a version >= "6.1.0" (e.g., "^6.1.0") so the linter supports React 19.2
hook semantics like useEffectEvent; also run npm/yarn install afterwards to
refresh lockfiles and ensure the new plugin is picked up by ESLint configuration
that references eslint-plugin-react-hooks.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 560e3259-b1b3-48b5-99f9-f94a6c13c224
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (29)
.github/workflows/autofix.yml.github/workflows/claude.yml.github/workflows/e2e-tests.yml.github/workflows/pr.yml.github/workflows/release.yml.github/workflows/reproduce-and-fix-issue-claude.yml.github/workflows/review-pr-claude.yml.tool-versionsexamples/angular/todos/package.jsonexamples/react-native/offline-transactions/android/gradle/wrapper/gradle-wrapper.propertiesexamples/react-native/offline-transactions/package.jsonexamples/react/offline-transactions/package.jsonexamples/react/paced-mutations-demo/package.jsonexamples/react/projects/package.jsonexamples/react/todo/package.jsonexamples/solid/todo/package.jsonpackage.jsonpackages/angular-db/package.jsonpackages/db-collection-e2e/package.jsonpackages/db/package.jsonpackages/electric-db-collection/package.jsonpackages/offline-transactions/package.jsonpackages/powersync-db-collection/package.jsonpackages/react-db/package.jsonpackages/rxdb-db-collection/package.jsonpackages/solid-db/package.jsonpackages/svelte-db/package.jsonpackages/trailbase-db-collection/package.jsonpackages/vue-db/package.json
🚧 Files skipped from review as they are similar to previous changes (18)
- packages/svelte-db/package.json
- packages/trailbase-db-collection/package.json
- .github/workflows/release.yml
- packages/react-db/package.json
- examples/react/offline-transactions/package.json
- packages/vue-db/package.json
- examples/react/paced-mutations-demo/package.json
- .github/workflows/pr.yml
- examples/react/projects/package.json
- packages/angular-db/package.json
- .tool-versions
- packages/electric-db-collection/package.json
- .github/workflows/review-pr-claude.yml
- .github/workflows/reproduce-and-fix-issue-claude.yml
- packages/solid-db/package.json
- .github/workflows/e2e-tests.yml
- .github/workflows/claude.yml
- examples/angular/todos/package.json
| "expo": "~53.0.27", | ||
| "expo-constants": "~17.1.8", | ||
| "expo-linking": "~7.1.7", | ||
| "expo-router": "~5.1.11", | ||
| "expo-status-bar": "~2.2.0", | ||
| "metro": "0.82.5", | ||
| "expo-status-bar": "~2.2.3", | ||
| "metro": "0.84.2", | ||
| "react": "^19.2.4", | ||
| "react-native": "0.79.6", | ||
| "react-native-safe-area-context": "5.4.0", | ||
| "react-native-screens": "~4.11.1", | ||
| "react-native": "0.84.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
What React Native and Metro versions are officially supported by Expo SDK 53.0.27, and is react-native 0.84.1 with metro 0.84.2 supported?
💡 Result:
- Expo SDK 53.0.27 officially targets React Native
0.79.x(SDK 53 “includes React Native 0.79”). [1] - Metro: React Native 0.79 ships with Metro
0.82, and that’s the Metro version Expo SDK 53 is effectively aligned with. [2] - Expo’s policy is that each Expo SDK targets a single React Native version (so other RN majors aren’t “officially supported” for that SDK). [3]
So: react-native@0.84.1 with metro@0.84.2 is not officially supported on Expo SDK 53.0.27 (it’s outside the RN 0.79 target). [3]
Sources: [1] https://expo.dev/changelog/sdk-53, [2] https://reactnative.dev/blog/2025/04/08/react-native-0.79, [3] https://docs.expo.dev/versions/latest/
Update react-native and metro to versions compatible with Expo SDK 53.
Expo SDK 53.0.27 officially targets React Native 0.79.x (which ships with Metro 0.82), but the current versions are react-native 0.84.1 and metro 0.84.2. These are outside the supported compatibility matrix and will cause runtime issues in the managed workflow. Update to React Native 0.79.x and Metro 0.82.x.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@examples/react-native/offline-transactions/package.json` around lines 21 -
28, Update the package.json dependency versions for react-native and metro to
Expo SDK 53-compatible releases: change "react-native" from 0.84.1 to a 0.79.x
version and "metro" from 0.84.2 to 0.82.x so they match Expo SDK 53 (e.g.,
react-native 0.79.x and metro 0.82.x); ensure you update any lockfile (yarn.lock
or package-lock.json) and reinstall dependencies so the managed workflow uses
the supported RN/Metro pair.
| "eslint": "^9.39.4", | ||
| "eslint-plugin-react-hooks": "^5.2.0", | ||
| "eslint-plugin-react-refresh": "^0.4.26", | ||
| "pg": "^8.18.0", | ||
| "eslint-plugin-react-refresh": "^0.5.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
For React 19.2, what is the minimum required version of eslint-plugin-react-hooks, and does v5.2.0 satisfy it?
💡 Result:
React 19.2 expects eslint-plugin-react-hooks v6 (the first “official” v6 release is v6.1.0, since v6.0.0 was accidentally released/deprecated) so that linting understands useEffectEvent and doesn’t treat Effect Events as effect dependencies. [1][2]
Therefore, eslint-plugin-react-hooks@5.2.0 does not satisfy the minimum expected version for React 19.2. [1][2]
React 19.2 requires eslint-plugin-react-hooks v6.1.0 or higher; Line 41 is on v5.2.0.
The version on Line 41 (eslint-plugin-react-hooks@^5.2.0) does not support React 19.2's new hook semantics, specifically useEffectEvent. This causes the linter to miss or misreport hook dependency checks. Upgrade to at least v6.1.0 (v6.0.0 was deprecated).
Required package.json adjustment
- "eslint-plugin-react-hooks": "^5.2.0",
+ "eslint-plugin-react-hooks": "^6.1.0",🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@examples/react/todo/package.json` around lines 40 - 42, Update the
eslint-plugin-react-hooks dependency in package.json: replace the current
"eslint-plugin-react-hooks": "^5.2.0" entry with a version >= "6.1.0" (e.g.,
"^6.1.0") so the linter supports React 19.2 hook semantics like useEffectEvent;
also run npm/yarn install afterwards to refresh lockfiles and ensure the new
plugin is picked up by ESLint configuration that references
eslint-plugin-react-hooks.
This PR contains the following updates:
^20.3.16→^20.3.20^20.3.16→^20.3.20^20.3.16→^20.3.18^20.3.16→^20.3.18^20.3.16→^20.3.18^20.3.16→^20.3.18^20.3.16→^20.3.18^20.3.16→^20.3.18^20.3.16→^20.3.18^20.3.16→^20.3.18^20.3.16→^20.3.18^20.3.16→^20.3.18^20.3.16→^20.3.18^20.3.16→^20.3.18^2.29.8→^2.30.0^9.39.2→^9.39.4^9.39.2→^9.39.4^9.39.2→^9.39.4^0.2.0→^0.3.0^1.46.0→^1.49.0^0.15.2→^0.18.12.1.2→2.2.011.4.1→11.5.211.4.1→11.5.2^0.7.2→^0.7.3^4.1.18→^4.2.1^4.1.18→^4.2.1^4.1.18→^4.2.1^4.1.18→^4.2.10.3.4→0.4.0^5.90.20→^5.90.21^1.159.5→^1.167.0^1.159.5→^1.167.0^1.159.5→^1.167.0^1.159.5→^1.166.7^1.159.5→^1.166.7^1.159.5→^1.166.11^1.159.5→^1.166.11^1.159.5→^1.166.11^1.159.5→^1.166.9^1.159.5→^1.167.0^1.159.5→^1.166.11^0.8.0→^0.9.20.4.3→0.5.0^11.10.0→^11.12.0^8.16.0→^8.18.0^8.16.0→^8.18.0^8.16.0→^8.18.0^19.2.13→^19.2.14^19.2.13→^19.2.14^19.2.13→^19.2.14^8.55.0→^8.57.0^8.55.0→^8.57.0^8.55.0→^8.57.0^8.55.0→^8.57.0^8.55.0→^8.57.0^8.55.0→^8.57.0^5.1.3→^5.2.0^6.0.4→^6.0.5v6.0.1→v6.0.2^2.1.29→^2.2.0v1.5.3→v1.7.0^17.2.4→^17.3.1^9.39.2→^9.39.4^9.39.2→^9.39.4^9.39.2→^9.39.4^0.4.26→^0.5.2~53.0.26→~53.0.27~17.1.0→~17.1.8~7.1.0→~7.1.7~2.2.0→~2.2.3^3.23.0→^3.23.28.13→8.14.4~2.1.0→~2.2.0^5.83.1→^5.86.00.82.5→0.84.20.82.5→0.84.2^8.18.0→^8.20.0^8.18.0→^8.20.0^8.18.0→^8.20.0^8.18.0→^8.20.010.27.0→10.32.110.27.0→10.32.110.26.0→10.32.1^8.5.6→^8.5.8^0.3.17→^0.3.180.79.6→0.84.10.79.6→0.84.15.4.0→5.7.0~4.11.1→~4.24.0^5.50.0→^5.53.12^4.3.6→^4.4.5^4.1.18→^4.2.1^4.1.18→^4.2.1^4.1.18→^4.2.1^0.3.0→^0.3.2^0.8.0→^0.9.1^7.3.0→^7.3.1^7.3.0→^7.3.1^2.11.10→^2.11.11^3.5.28→^3.5.30~0.15.0→~0.16.1~0.15.0→~0.16.1Release Notes
angular/angular-cli (@angular/build)
v20.3.20Compare Source
@angular/build
v20.3.19Compare Source
@angular-devkit/build-angular
angular/angular (@angular/common)
v20.3.18Compare Source
compiler
core
changesets/changesets (@changesets/cli)
v2.30.0Compare Source
eslint/eslint (@eslint/js)
v9.39.4Compare Source
dubzzz/fast-check (@fast-check/vitest)
v0.3.0Support
beforeEach/afterEachhooks and ESM-only bundle[Code][Diff]
Breaking changes
beforeEach/afterEachin@fast-check/vitestFixes
powersync-ja/powersync-js (@powersync/common)
v1.49.0Compare Source
Minor Changes
8ff6b3e: AddedsetupContextoption toCreateDiffTriggerOptionsand a lock context option to the cleanup function returned bycreateDiffTrigger, this allows you to create and dispose of a trigger inside of a lock context.42afb0e: Share common db adapter implementation logic.v1.48.0Compare Source
Minor Changes
6c855cd: Improve raw tables by makingputanddeletestatements optional if a local name is given.react-native-async-storage/async-storage (@react-native-async-storage/async-storage)
v2.2.0Compare Source
Minor Changes
8b2f32b: Fix support for React Native 0.80react-native-netinfo/react-native-netinfo (@react-native-community/netinfo)
v11.5.2Compare Source
Bug Fixes
v11.5.1Compare Source
Bug Fixes
v11.5.0Compare Source
Bug Fixes
Features
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.