chore(deps): update all non-major dependencies#10780
Conversation
|
|
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:
📝 WalkthroughWalkthroughRepository-wide dependency and tooling version updates across examples, integrations, packages, pnpm workspace overrides, and a single CI action pin bump. ChangesDependency Version Upgrades
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
View your CI Pipeline Execution ↗ for commit bb78924 ☁️ Nx Cloud last updated this comment at |
![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 current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@examples/angular/auto-refetching/package.json`:
- Around line 12-24: Update the explicit zone.js pin in package.json so it
matches Angular 20.3.x peer requirements: in the dependencies section update or
remove the "zone.js" entry (the "zone.js" dependency key in
examples/angular/auto-refetching/package.json) — either set it to the
peer-compatible range "~0.15.0" or remove the explicit pin so the Angular
CLI/tooling can manage it; apply the same change to the other Angular example
package.json files that currently pin "zone.js" to 0.16.2.
In `@examples/react/react-native/package.json`:
- Line 19: The package.json pins "expo" and "react-native" to incompatible
versions; update the dependency pairing so Expo SDK 52 is paired with RN 0.76
(default) or 0.77 (opt-in) or alternatively bump "expo" to an SDK that
officially supports RN 0.85.x; edit the "expo" and/or "react-native" entries in
package.json (the "expo" and "react-native" keys) to a compatible version match,
then reinstall and update the lockfile (yarn.lock/package-lock.json) and re-run
Expo validation to verify the fix.
In `@examples/vue/2.6-basic/package.json`:
- Around line 14-15: The package.json lists "vue": "2.6.14" but
"vue-template-compiler": "2.7.16", causing a Vue 2 build break; update the
"vue-template-compiler" dependency value to exactly match "vue" (set
"vue-template-compiler": "2.6.14") so both versions are identical, then
reinstall dependencies (npm/yarn) and update lockfile; verify builds to ensure
the mismatch is resolved.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 4d01be9d-da0f-45d3-9bba-5021f0ab871e
📒 Files selected for processing (93)
.github/workflows/zizmor.ymlexamples/angular/auto-refetching/package.jsonexamples/angular/basic-persister/package.jsonexamples/angular/basic/package.jsonexamples/angular/devtools-panel/package.jsonexamples/angular/infinite-query-with-max-pages/package.jsonexamples/angular/optimistic-updates/package.jsonexamples/angular/pagination/package.jsonexamples/angular/query-options-from-a-service/package.jsonexamples/angular/router/package.jsonexamples/angular/rxjs/package.jsonexamples/angular/simple/package.jsonexamples/lit/basic/package.jsonexamples/lit/pagination/package.jsonexamples/lit/ssr/package.jsonexamples/preact/simple/package.jsonexamples/react/algolia/package.jsonexamples/react/basic-graphql-request/package.jsonexamples/react/basic/package.jsonexamples/react/chat/package.jsonexamples/react/default-query-function/package.jsonexamples/react/devtools-panel/package.jsonexamples/react/eslint-legacy/package.jsonexamples/react/eslint-plugin-demo/package.jsonexamples/react/offline/package.jsonexamples/react/playground/package.jsonexamples/react/react-native/package.jsonexamples/react/react-router/package.jsonexamples/react/rick-morty/package.jsonexamples/react/shadow-dom/package.jsonexamples/react/simple/package.jsonexamples/react/star-wars/package.jsonexamples/react/suspense/package.jsonexamples/solid/astro/package.jsonexamples/solid/basic-graphql-request/package.jsonexamples/solid/basic/package.jsonexamples/solid/default-query-function/package.jsonexamples/solid/offline/package.jsonexamples/solid/simple/package.jsonexamples/solid/solid-start-streaming/package.jsonexamples/svelte/auto-refetching/package.jsonexamples/svelte/basic/package.jsonexamples/svelte/load-more-infinite-scroll/package.jsonexamples/svelte/optimistic-updates/package.jsonexamples/svelte/playground/package.jsonexamples/svelte/simple/package.jsonexamples/svelte/ssr/package.jsonexamples/svelte/star-wars/package.jsonexamples/vue/2.6-basic/package.jsonexamples/vue/2.7-basic/package.jsonexamples/vue/basic/package.jsonexamples/vue/dependent-queries/package.jsonexamples/vue/nuxt3/package.jsonexamples/vue/persister/package.jsonexamples/vue/simple/package.jsonintegrations/angular-cli-20/package.jsonintegrations/lit-vite/package.jsonintegrations/react-next-15/package.jsonintegrations/react-next-16/package.jsonintegrations/react-vite/package.jsonintegrations/react-webpack-4/package.jsonintegrations/react-webpack-5/package.jsonintegrations/solid-vite/package.jsonintegrations/svelte-vite/package.jsonintegrations/vue-vite/package.jsonpackage.jsonpackages/angular-query-experimental/package.jsonpackages/angular-query-persist-client/package.jsonpackages/eslint-plugin-query/package.jsonpackages/lit-query/package.jsonpackages/preact-query-devtools/package.jsonpackages/preact-query-persist-client/package.jsonpackages/preact-query/package.jsonpackages/query-async-storage-persister/package.jsonpackages/query-broadcast-client-experimental/package.jsonpackages/query-core/package.jsonpackages/query-devtools/package.jsonpackages/query-persist-client-core/package.jsonpackages/query-sync-storage-persister/package.jsonpackages/query-test-utils/package.jsonpackages/react-query-devtools/package.jsonpackages/react-query-next-experimental/package.jsonpackages/react-query-persist-client/package.jsonpackages/react-query/package.jsonpackages/solid-query-devtools/package.jsonpackages/solid-query-persist-client/package.jsonpackages/solid-query/package.jsonpackages/svelte-query-devtools/package.jsonpackages/svelte-query-persist-client/package.jsonpackages/svelte-query/package.jsonpackages/vue-query-devtools/package.jsonpackages/vue-query/package.jsonpnpm-workspace.yaml
| "@angular/common": "^20.3.21", | ||
| "@angular/compiler": "^20.3.21", | ||
| "@angular/core": "^20.3.21", | ||
| "@angular/platform-browser": "^20.3.21", | ||
| "@tanstack/angular-query-experimental": "^5.100.14", | ||
| "rxjs": "^7.8.2", | ||
| "tslib": "^2.8.1", | ||
| "zone.js": "0.15.0" | ||
| "zone.js": "0.16.2" | ||
| }, | ||
| "devDependencies": { | ||
| "@angular/build": "^20.0.0", | ||
| "@angular/cli": "^20.0.0", | ||
| "@angular/compiler-cli": "^20.0.0", | ||
| "@angular/build": "^20.3.26", | ||
| "@angular/cli": "^20.3.26", | ||
| "@angular/compiler-cli": "^20.3.21", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check Angular 20.3.x and zone.js 0.16.2 existence and compatibility
echo "=== Checking Angular versions ==="
npm view `@angular/core`@20.3.21 version 2>/dev/null || echo "❌ `@angular/core`@20.3.21 not found"
npm view `@angular/build`@20.3.26 version 2>/dev/null || echo "❌ `@angular/build`@20.3.26 not found"
echo -e "\n=== Checking zone.js version ==="
npm view zone.js@0.16.2 version 2>/dev/null || echo "❌ zone.js@0.16.2 not found"
echo -e "\n=== Checking zone.js peer dependency requirements ==="
npm view zone.js@0.16.2 peerDependencies 2>/dev/null
echo -e "\n=== Checking Angular 20.3.21 zone.js compatibility ==="
npm view `@angular/core`@20.3.21 peerDependencies 2>/dev/null | grep -i zone || echo "No zone.js peer dependency listed"
echo -e "\n=== Security advisories check ==="
npm audit --package-lock-only --json 2>/dev/null | jq '.vulnerabilities | length' || echo "Run npm audit after install"Repository: TanStack/query
Length of output: 321
🌐 Web query:
Angular 20.3 zone.js 0.16 compatibility requirements
💡 Result:
Angular 20.3 compatibility with zone.js 0.16 (as of 2026-05-25): - I did not find an authoritative source that explicitly states “Angular 20.3.x requires zone.js 0.16.x”. - Angular’s official version compatibility table (for Angular 20.x and 21.x, etc.) lists Node.js and TypeScript/RxJS requirements, but does not list a specific zone.js version for Angular 20.3.x in the table [1]. - Angular’s own zone.js documentation focuses on the move toward zoneless change detection and does not provide a per-Angular-version zone.js matrix [2]. - There is evidence that Angular dropped support for very old zone.js versions (<= 0.12.0) [3], which implies “not 0.12 or older”, but it still doesn’t confirm “0.16 is required/compatible” for 20.3 specifically [3]. What you can safely conclude / requirements to follow: 1) Don’t manually pin zone.js to 0.16 for Angular 20.3 unless your Angular toolchain pins it. - The safest approach is to let the Angular CLI / ng update manage the zone.js dependency rather than guessing a matching minor/patch line [3]. 2) If you want to eliminate zone.js compatibility requirements entirely, use zoneless mode. - Angular’s zoneless guide says that zoneless apps should remove ZoneJS from the build (remove zone.js and zone.js/testing from polyfills) and can uninstall the dependency [4]. If you tell me your exact Angular package versions (e.g., @angular/core 20.3.xx), your Angular CLI version, and your current zone.js semver range (from package.json), I can do one more targeted search for any explicit “works with” statement tied to that exact patch version.
Citations:
- 1: https://angular.dev/reference/versions
- 2: https://github.com/angular/angular/blob/main/packages/zone.js/README.md
- 3: feat(core): drop support for
zone.jsversions<=0.12.0angular/angular#49331 - 4: https://github.com/angular/angular/blob/main/adev/src/content/guide/zoneless.md
Fix zone.js pin for Angular 20.3.x examples
@angular/core@20.3.21 and @angular/build@20.3.26 and zone.js@0.16.2 are published, but @angular/core@20.3.21 declares a peer dependency zone.js: ~0.15.0, so pinning zone.js to 0.16.2 is outside Angular’s declared range and may cause install/runtime issues. Revert to the version range Angular tooling expects (or remove the explicit zone.js pin so Angular CLI manages it) in examples/angular/auto-refetching/package.json (and the other affected Angular examples).
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@examples/angular/auto-refetching/package.json` around lines 12 - 24, Update
the explicit zone.js pin in package.json so it matches Angular 20.3.x peer
requirements: in the dependencies section update or remove the "zone.js" entry
(the "zone.js" dependency key in examples/angular/auto-refetching/package.json)
— either set it to the peer-compatible range "~0.15.0" or remove the explicit
pin so the Angular CLI/tooling can manage it; apply the same change to the other
Angular example package.json files that currently pin "zone.js" to 0.16.2.
| "expo": "^52.0.11", | ||
| "expo-constants": "^17.0.3", | ||
| "expo-status-bar": "^2.0.0", | ||
| "expo": "^52.0.49", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Read-only check: surface Expo/RN versions in this example.
jq -r '.dependencies | {expo, react, "react-native", "react-native-web"}' examples/react/react-native/package.json
# Optional: validate against Expo's expected SDK mapping in docs.
# Expected for SDK 52: RN 0.76 (0.77 supported), not 0.85.Repository: TanStack/query
Length of output: 167
🌐 Web query:
What React Native versions are supported by Expo SDK 52, and does Expo SDK 52 support React Native 0.85.x?
💡 Result:
Expo SDK 52 supports React Native 0.76 by default (Expo SDK reference table shows SDK 52.0.0 → React Native 0.76) [1][2]. Expo SDK 52 can also be used with React Native 0.77 via an opt-in path (Expo changelog states “The default React Native version for Expo SDK 52 will continue to be 0.76” and that you can “opt in to use version 0.77”) [3]. No, Expo SDK 52 does not support React Native 0.85.x. The official Expo changelog for SDK 52 discusses React Native 0.76 (default) and an opt-in to 0.77, and does not mention 0.85.x compatibility [3]. Additionally, the current Expo SDK reference table indicates that React Native 0.85 corresponds to Expo SDK 56, not SDK 52 (SDK 56.0.0 → React Native 0.85) [4]. Answer: Supported RN versions in Expo SDK 52 are 0.76.x by default and 0.77.x via opt-in; Expo SDK 52 does not support React Native 0.85.x [1][3][4].
Citations:
- 1: https://docs.expo.io/versions/v53.0.0
- 2: https://docs.expo.dev/versions/latest/?redirected=
- 3: https://expo.dev/changelog/2025-01-21-react-native-0.77
- 4: https://docs.expo.dev/versions/latest/
Fix Expo SDK 52 ↔ React Native 0.85 version mismatch
This example pins "expo": "^52.0.49" and "react-native": "^0.85.3", but Expo SDK 52 supports React Native 0.76 (default) / 0.77 (opt-in) and does not support 0.85.x. This is likely to break Expo validation/build flows—update either react-native to 0.76/0.77 or bump expo to the SDK that matches RN 0.85.x.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@examples/react/react-native/package.json` at line 19, The package.json pins
"expo" and "react-native" to incompatible versions; update the dependency
pairing so Expo SDK 52 is paired with RN 0.76 (default) or 0.77 (opt-in) or
alternatively bump "expo" to an SDK that officially supports RN 0.85.x; edit the
"expo" and/or "react-native" entries in package.json (the "expo" and
"react-native" keys) to a compatible version match, then reinstall and update
the lockfile (yarn.lock/package-lock.json) and re-run Expo validation to verify
the fix.
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
9e29cfb to
4ed2a06
Compare
There was a problem hiding this comment.
Actionable comments posted: 12
♻️ Duplicate comments (2)
examples/angular/auto-refetching/package.json (1)
12-24:⚠️ Potential issue | 🟠 Major | ⚡ Quick winzone.js 0.16.2 remains incompatible with Angular 20.3.21.
This issue was already flagged in the previous review: Angular 20.3.21 declares
zone.js: ~0.15.0as a peer dependency, but this manifest pins0.16.2. This mismatch will cause installation errors or runtime incompatibilities.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@examples/angular/auto-refetching/package.json` around lines 12 - 24, The package manifest pins "zone.js" to "0.16.2" which is incompatible with Angular 20.3.21 (Angular declares peer dependency ~0.15.0); change the "zone.js" dependency in package.json from "0.16.2" to a version compatible with Angular (e.g., "~0.15.0"), update any related lockfile, and run an install to verify peer-dependency resolution for the Angular packages ("`@angular/core`", "`@angular/common`", etc.).examples/vue/2.6-basic/package.json (1)
14-15:⚠️ Potential issue | 🔴 Critical | ⚡ Quick winCritical: Match
vue-template-compilerto the Vue 2 runtime version
examples/vue/2.6-basic/package.jsonsets"vue": "2.6.14"but"vue-template-compiler": "2.7.16". Vue 2 tooling expects the compiler package to be the same Vue 2 version as the runtime to avoid “Vue packages version mismatch” and compiler/runtime incompatibilities.🔧 Proposed fix
"vue": "2.6.14", -"vue-template-compiler": "2.7.16" +"vue-template-compiler": "2.6.14"🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@examples/vue/2.6-basic/package.json` around lines 14 - 15, The package.json currently has a Vue runtime/version mismatch: "vue": "2.6.14" but "vue-template-compiler": "2.7.16"; update the "vue-template-compiler" dependency to exactly match the runtime version (set "vue-template-compiler": "2.6.14") so the compiler and runtime versions align, then reinstall dependencies (npm install or yarn) to apply the change; locate and edit the dependency entries for "vue" and "vue-template-compiler" in package.json to make this change.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@examples/angular/basic-persister/package.json`:
- Around line 12-27: The package manifest pins zone.js to "0.16.2" which
conflicts with Angular 20.3.21's peer dependency (~0.15.0); update the
dependency entry for "zone.js" in package.json to use a compatible range (e.g.,
"~0.15.0") or remove the explicit "zone.js" entry so npm/yarn can resolve the
peer-compatible version, ensuring other entries like "`@angular/core`" and
"`@angular/compiler`" remain unchanged.
In `@examples/angular/devtools-panel/package.json`:
- Around line 12-27: The package.json currently pins "zone.js" to "0.16.2" which
conflicts with Angular 20.3.21's peer dependency; update the "zone.js" entry in
package.json (the dependency key "zone.js") to "~0.15.0" or remove the explicit
"zone.js" version to let npm resolve a compatible version, then reinstall
dependencies to ensure peer constraints are satisfied.
In `@examples/angular/optimistic-updates/package.json`:
- Around line 12-27: The package.json currently pins "zone.js": "0.16.2" which
conflicts with Angular 20.3.21's peer dependency; update the dependency entry
for "zone.js" (the literal key "zone.js" in package.json) to a compatible spec
such as "~0.15.0" or remove the explicit "zone.js" entry entirely so the Angular
peer dependency can be satisfied during install.
In `@examples/angular/pagination/package.json`:
- Around line 12-26: The package.json currently pins "zone.js" to "0.16.2" which
conflicts with the Angular peer dependency; update the dependencies entry for
"zone.js" (in the examples/angular/pagination package.json) to use the
compatible range "~0.15.0" or remove the explicit "zone.js" entry so it can
resolve to the peer-compatible version, ensuring the rest of the deps (e.g.,
"`@angular/core`" / "`@angular/common`" versions) remain unchanged.
In `@examples/angular/query-options-from-a-service/package.json`:
- Around line 12-27: The package.json currently pins "zone.js" to "0.16.2",
which violates the Angular 20.3.x peer dependency (expects ~0.15.0); update the
"zone.js" entry in package.json (near the other Angular deps like
"`@angular/core`", "`@angular/common`") to "~0.15.0" or remove the explicit
"zone.js" pin so npm/yarn can resolve a compatible ~0.15.x version to satisfy
the Angular peer dependency.
In `@examples/angular/router/package.json`:
- Around line 12-27: The package manifest pins zone.js to 0.16.2 which violates
Angular 20.3.21's peer dependency (~0.15.0); open
examples/angular/router/package.json and change the "zone.js" dependency entry
from "0.16.2" to "~0.15.0" (or remove the explicit "zone.js" entry entirely) so
it satisfies `@angular/core/`@angular/common peer requirements and prevents
install errors.
In `@examples/angular/rxjs/package.json`:
- Around line 12-27: The package.json currently pins "zone.js" to "0.16.2",
which conflicts with Angular 20.3.21's peer dependency (~0.15.0); update the
dependency entry for "zone.js" in package.json to use "~0.15.0" (or remove the
explicit "zone.js" entry so the Angular peer resolution can apply) to satisfy
Angular's peer requirement and avoid install errors.
In `@integrations/angular-cli-20/package.json`:
- Line 20: The package.json change pins "zone.js" to "~0.16.2" which is fine for
Angular 20.3 but may remove IE/non‑Chromium Edge support; update the PR by
verifying your browserslist/target matrix (e.g., browserslist file or build
config) and either revert to a compatible zone.js range or document/confirm that
IE and legacy Edge are intentionally unsupported; explicitly note the decision
in the package.json commit message or README so consumers know why "zone.js":
"~0.16.2" was chosen.
In `@integrations/react-next-15/package.json`:
- Line 9: The package.json bump to "`@js-temporal/polyfill`" ^0.5.1 introduces
breaking API changes; audit the integrations/react-next-15 code for any Temporal
APIs and update call sites: replace uses of Temporal.ZonedDateTime where passed
to Intl.DateTimeFormat by converting to compatible types or formatting strings,
change all .timeZone and Temporal.Now.timeZone to .timeZoneId, replace removed
helpers like getISOFields, withPlainDate, withPlainDateTime,
Instant.fromEpochSeconds/fromEpochMicroseconds and
epochSeconds/epochMicroseconds with the new equivalent constructors and
conversion routines, update Duration.prototype.add/subtract call sites to the
new signatures (remove relativeTo parameter), and review any code relying on
looser zone offset precision; update imports/usages and tests accordingly to the
v0.5.0 API.
In `@integrations/svelte-vite/package.json`:
- Line 12: The Svelte upgrade in package.json (the "svelte" version bump to
^5.55.9) can introduce breaking compiler/runtime/SSR changes; verify
compatibility by running the repo's test suite and QA flows and fix code where
needed: ensure any component templates place let: before {`@const`} and update all
{`#each` ... key} blocks to include the required "as" clause, inspect usages of
unset_context/current_batch to account for changed batching semantics, review
SSR/hydration code and tests for hydration marker changes and error-boundary
behavior, and audit contenteditable bindings and any transformError usage for
sanitization/HTML-comment embedding differences, adjusting components or test
expectations accordingly.
In `@packages/angular-query-experimental/package.json`:
- Around line 99-100: The plugin is being configured with externalizeDeps({
include: options.externalDeps ?? [] }) which likely uses the wrong option name
and will be ignored by the plugin; change the configuration in vite.config.ts to
use the documented option name (except) instead of include so you pass
externalizeDeps({ except: options.externalDeps ?? [] }) or otherwise map your
options to the plugin's expected API; verify the semantics (except lists deps
that should remain bundled) and keep the dependency version
("vite-plugin-externalize-deps": "^0.10.0") as-is unless you need to pin for
Vite compatibility.
In `@pnpm-workspace.yaml`:
- Line 40: The esbuild version constraint "esbuild" in pnpm-workspace.yaml is
set to '^0.28.0' which may introduce breaking changes (binary integrity checks
and updated Go toolchain); update the dependency constraint to a safe, tested
version (either pin to the previous working version or bump to a verified newer
release) and run CI/builds to validate; specifically, change the "esbuild" entry
in pnpm-workspace.yaml and then run the monorepo build/CI flows (including any
environments that trigger fallback binary downloads) to confirm no
integrity/hash failures or toolchain regressions.
---
Duplicate comments:
In `@examples/angular/auto-refetching/package.json`:
- Around line 12-24: The package manifest pins "zone.js" to "0.16.2" which is
incompatible with Angular 20.3.21 (Angular declares peer dependency ~0.15.0);
change the "zone.js" dependency in package.json from "0.16.2" to a version
compatible with Angular (e.g., "~0.15.0"), update any related lockfile, and run
an install to verify peer-dependency resolution for the Angular packages
("`@angular/core`", "`@angular/common`", etc.).
In `@examples/vue/2.6-basic/package.json`:
- Around line 14-15: The package.json currently has a Vue runtime/version
mismatch: "vue": "2.6.14" but "vue-template-compiler": "2.7.16"; update the
"vue-template-compiler" dependency to exactly match the runtime version (set
"vue-template-compiler": "2.6.14") so the compiler and runtime versions align,
then reinstall dependencies (npm install or yarn) to apply the change; locate
and edit the dependency entries for "vue" and "vue-template-compiler" in
package.json to make this change.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: b2bf2809-2be7-4420-b252-fde4704e43c2
📒 Files selected for processing (93)
.github/workflows/zizmor.ymlexamples/angular/auto-refetching/package.jsonexamples/angular/basic-persister/package.jsonexamples/angular/basic/package.jsonexamples/angular/devtools-panel/package.jsonexamples/angular/infinite-query-with-max-pages/package.jsonexamples/angular/optimistic-updates/package.jsonexamples/angular/pagination/package.jsonexamples/angular/query-options-from-a-service/package.jsonexamples/angular/router/package.jsonexamples/angular/rxjs/package.jsonexamples/angular/simple/package.jsonexamples/lit/basic/package.jsonexamples/lit/pagination/package.jsonexamples/lit/ssr/package.jsonexamples/preact/simple/package.jsonexamples/react/algolia/package.jsonexamples/react/basic-graphql-request/package.jsonexamples/react/basic/package.jsonexamples/react/chat/package.jsonexamples/react/default-query-function/package.jsonexamples/react/devtools-panel/package.jsonexamples/react/eslint-legacy/package.jsonexamples/react/eslint-plugin-demo/package.jsonexamples/react/offline/package.jsonexamples/react/playground/package.jsonexamples/react/react-native/package.jsonexamples/react/react-router/package.jsonexamples/react/rick-morty/package.jsonexamples/react/shadow-dom/package.jsonexamples/react/simple/package.jsonexamples/react/star-wars/package.jsonexamples/react/suspense/package.jsonexamples/solid/astro/package.jsonexamples/solid/basic-graphql-request/package.jsonexamples/solid/basic/package.jsonexamples/solid/default-query-function/package.jsonexamples/solid/offline/package.jsonexamples/solid/simple/package.jsonexamples/solid/solid-start-streaming/package.jsonexamples/svelte/auto-refetching/package.jsonexamples/svelte/basic/package.jsonexamples/svelte/load-more-infinite-scroll/package.jsonexamples/svelte/optimistic-updates/package.jsonexamples/svelte/playground/package.jsonexamples/svelte/simple/package.jsonexamples/svelte/ssr/package.jsonexamples/svelte/star-wars/package.jsonexamples/vue/2.6-basic/package.jsonexamples/vue/2.7-basic/package.jsonexamples/vue/basic/package.jsonexamples/vue/dependent-queries/package.jsonexamples/vue/nuxt3/package.jsonexamples/vue/persister/package.jsonexamples/vue/simple/package.jsonintegrations/angular-cli-20/package.jsonintegrations/lit-vite/package.jsonintegrations/react-next-15/package.jsonintegrations/react-next-16/package.jsonintegrations/react-vite/package.jsonintegrations/react-webpack-4/package.jsonintegrations/react-webpack-5/package.jsonintegrations/solid-vite/package.jsonintegrations/svelte-vite/package.jsonintegrations/vue-vite/package.jsonpackage.jsonpackages/angular-query-experimental/package.jsonpackages/angular-query-persist-client/package.jsonpackages/eslint-plugin-query/package.jsonpackages/lit-query/package.jsonpackages/preact-query-devtools/package.jsonpackages/preact-query-persist-client/package.jsonpackages/preact-query/package.jsonpackages/query-async-storage-persister/package.jsonpackages/query-broadcast-client-experimental/package.jsonpackages/query-core/package.jsonpackages/query-devtools/package.jsonpackages/query-persist-client-core/package.jsonpackages/query-sync-storage-persister/package.jsonpackages/query-test-utils/package.jsonpackages/react-query-devtools/package.jsonpackages/react-query-next-experimental/package.jsonpackages/react-query-persist-client/package.jsonpackages/react-query/package.jsonpackages/solid-query-devtools/package.jsonpackages/solid-query-persist-client/package.jsonpackages/solid-query/package.jsonpackages/svelte-query-devtools/package.jsonpackages/svelte-query-persist-client/package.jsonpackages/svelte-query/package.jsonpackages/vue-query-devtools/package.jsonpackages/vue-query/package.jsonpnpm-workspace.yaml
✅ Files skipped from review due to trivial changes (40)
- examples/react/suspense/package.json
- packages/query-test-utils/package.json
- packages/query-sync-storage-persister/package.json
- integrations/lit-vite/package.json
- integrations/react-next-16/package.json
- examples/vue/basic/package.json
- examples/react/shadow-dom/package.json
- packages/query-persist-client-core/package.json
- examples/vue/2.7-basic/package.json
- packages/react-query-next-experimental/package.json
- examples/react/eslint-plugin-demo/package.json
- packages/solid-query-devtools/package.json
- packages/query-async-storage-persister/package.json
- examples/solid/simple/package.json
- examples/svelte/load-more-infinite-scroll/package.json
- examples/solid/solid-start-streaming/package.json
- packages/solid-query/package.json
- examples/angular/basic/package.json
- examples/react/basic/package.json
- .github/workflows/zizmor.yml
- integrations/react-vite/package.json
- packages/react-query/package.json
- examples/svelte/basic/package.json
- examples/vue/persister/package.json
- examples/react/playground/package.json
- examples/solid/basic/package.json
- packages/angular-query-persist-client/package.json
- packages/preact-query/package.json
- examples/lit/basic/package.json
- examples/react/algolia/package.json
- integrations/react-webpack-4/package.json
- examples/react/devtools-panel/package.json
- packages/query-broadcast-client-experimental/package.json
- integrations/solid-vite/package.json
- packages/query-core/package.json
- examples/angular/infinite-query-with-max-pages/package.json
- examples/solid/offline/package.json
- packages/svelte-query-persist-client/package.json
- examples/solid/basic-graphql-request/package.json
- examples/svelte/optimistic-updates/package.json
| "@angular/common": "^20.3.21", | ||
| "@angular/compiler": "^20.3.21", | ||
| "@angular/core": "^20.3.21", | ||
| "@angular/platform-browser": "^20.3.21", | ||
| "@tanstack/angular-query-experimental": "^5.100.14", | ||
| "@tanstack/angular-query-persist-client": "^5.100.14", | ||
| "@tanstack/query-async-storage-persister": "^5.100.14", | ||
| "rxjs": "^7.8.2", | ||
| "tslib": "^2.8.1", | ||
| "zone.js": "0.15.0" | ||
| "zone.js": "0.16.2" | ||
| }, | ||
| "devDependencies": { | ||
| "@angular/build": "^20.0.0", | ||
| "@angular/cli": "^20.0.0", | ||
| "@angular/compiler-cli": "^20.0.0", | ||
| "@angular/build": "^20.3.26", | ||
| "@angular/cli": "^20.3.26", | ||
| "@angular/compiler-cli": "^20.3.21", | ||
| "typescript": "5.8.3" |
There was a problem hiding this comment.
zone.js version violates Angular peer dependency.
Angular 20.3.21 requires zone.js: ~0.15.0, but this manifest specifies 0.16.2. Revert zone.js to ~0.15.0 or remove the explicit pin to avoid installation errors.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@examples/angular/basic-persister/package.json` around lines 12 - 27, The
package manifest pins zone.js to "0.16.2" which conflicts with Angular 20.3.21's
peer dependency (~0.15.0); update the dependency entry for "zone.js" in
package.json to use a compatible range (e.g., "~0.15.0") or remove the explicit
"zone.js" entry so npm/yarn can resolve the peer-compatible version, ensuring
other entries like "`@angular/core`" and "`@angular/compiler`" remain unchanged.
| "@angular/common": "^20.3.21", | ||
| "@angular/compiler": "^20.3.21", | ||
| "@angular/core": "^20.3.21", | ||
| "@angular/platform-browser": "^20.3.21", | ||
| "@angular/router": "^20.3.21", | ||
| "@tanstack/angular-query-experimental": "^5.100.14", | ||
| "rxjs": "^7.8.2", | ||
| "tslib": "^2.8.1", | ||
| "zone.js": "0.15.0" | ||
| "zone.js": "0.16.2" | ||
| }, | ||
| "devDependencies": { | ||
| "@angular/build": "^20.0.0", | ||
| "@angular/cli": "^20.0.0", | ||
| "@angular/compiler-cli": "^20.0.0", | ||
| "@angular/build": "^20.3.26", | ||
| "@angular/cli": "^20.3.26", | ||
| "@angular/compiler-cli": "^20.3.21", | ||
| "typescript": "5.8.3" | ||
| } |
There was a problem hiding this comment.
zone.js version violates Angular peer dependency.
Angular 20.3.21 requires zone.js: ~0.15.0, but this manifest specifies 0.16.2. Revert zone.js to ~0.15.0 or remove the explicit pin to avoid installation errors.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@examples/angular/devtools-panel/package.json` around lines 12 - 27, The
package.json currently pins "zone.js" to "0.16.2" which conflicts with Angular
20.3.21's peer dependency; update the "zone.js" entry in package.json (the
dependency key "zone.js") to "~0.15.0" or remove the explicit "zone.js" version
to let npm resolve a compatible version, then reinstall dependencies to ensure
peer constraints are satisfied.
| "@angular/common": "^20.3.21", | ||
| "@angular/compiler": "^20.3.21", | ||
| "@angular/core": "^20.3.21", | ||
| "@angular/forms": "^20.3.21", | ||
| "@angular/platform-browser": "^20.3.21", | ||
| "@tanstack/angular-query-experimental": "^5.100.14", | ||
| "rxjs": "^7.8.2", | ||
| "tslib": "^2.8.1", | ||
| "zone.js": "0.15.0" | ||
| "zone.js": "0.16.2" | ||
| }, | ||
| "devDependencies": { | ||
| "@angular/build": "^20.0.0", | ||
| "@angular/cli": "^20.0.0", | ||
| "@angular/compiler-cli": "^20.0.0", | ||
| "@angular/build": "^20.3.26", | ||
| "@angular/cli": "^20.3.26", | ||
| "@angular/compiler-cli": "^20.3.21", | ||
| "typescript": "5.8.3" | ||
| } |
There was a problem hiding this comment.
zone.js version violates Angular peer dependency.
Angular 20.3.21 requires zone.js: ~0.15.0, but this manifest specifies 0.16.2. Revert zone.js to ~0.15.0 or remove the explicit pin to avoid installation errors.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@examples/angular/optimistic-updates/package.json` around lines 12 - 27, The
package.json currently pins "zone.js": "0.16.2" which conflicts with Angular
20.3.21's peer dependency; update the dependency entry for "zone.js" (the
literal key "zone.js" in package.json) to a compatible spec such as "~0.15.0" or
remove the explicit "zone.js" entry entirely so the Angular peer dependency can
be satisfied during install.
| "@angular/common": "^20.3.21", | ||
| "@angular/compiler": "^20.3.21", | ||
| "@angular/core": "^20.3.21", | ||
| "@angular/platform-browser": "^20.3.21", | ||
| "@tanstack/angular-query-experimental": "^5.100.14", | ||
| "rxjs": "^7.8.2", | ||
| "tslib": "^2.8.1", | ||
| "zone.js": "0.15.0" | ||
| "zone.js": "0.16.2" | ||
| }, | ||
| "devDependencies": { | ||
| "@angular/build": "^20.0.0", | ||
| "@angular/cli": "^20.0.0", | ||
| "@angular/compiler-cli": "^20.0.0", | ||
| "@angular/build": "^20.3.26", | ||
| "@angular/cli": "^20.3.26", | ||
| "@angular/compiler-cli": "^20.3.21", | ||
| "typescript": "5.8.3" | ||
| } |
There was a problem hiding this comment.
zone.js version violates Angular peer dependency.
Angular 20.3.21 requires zone.js: ~0.15.0, but this manifest specifies 0.16.2. Revert zone.js to ~0.15.0 or remove the explicit pin to avoid installation errors.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@examples/angular/pagination/package.json` around lines 12 - 26, The
package.json currently pins "zone.js" to "0.16.2" which conflicts with the
Angular peer dependency; update the dependencies entry for "zone.js" (in the
examples/angular/pagination package.json) to use the compatible range "~0.15.0"
or remove the explicit "zone.js" entry so it can resolve to the peer-compatible
version, ensuring the rest of the deps (e.g., "`@angular/core`" /
"`@angular/common`" versions) remain unchanged.
| "@angular/common": "^20.3.21", | ||
| "@angular/compiler": "^20.3.21", | ||
| "@angular/core": "^20.3.21", | ||
| "@angular/platform-browser": "^20.3.21", | ||
| "@angular/router": "^20.3.21", | ||
| "@tanstack/angular-query-experimental": "^5.100.14", | ||
| "rxjs": "^7.8.2", | ||
| "tslib": "^2.8.1", | ||
| "zone.js": "0.15.0" | ||
| "zone.js": "0.16.2" | ||
| }, | ||
| "devDependencies": { | ||
| "@angular/build": "^20.0.0", | ||
| "@angular/cli": "^20.0.0", | ||
| "@angular/compiler-cli": "^20.0.0", | ||
| "@angular/build": "^20.3.26", | ||
| "@angular/cli": "^20.3.26", | ||
| "@angular/compiler-cli": "^20.3.21", | ||
| "typescript": "5.8.3" | ||
| } |
There was a problem hiding this comment.
zone.js version violates Angular peer dependency.
Angular 20.3.21 requires zone.js: ~0.15.0, but this manifest specifies 0.16.2. Revert zone.js to ~0.15.0 or remove the explicit pin to avoid installation errors.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@examples/angular/query-options-from-a-service/package.json` around lines 12 -
27, The package.json currently pins "zone.js" to "0.16.2", which violates the
Angular 20.3.x peer dependency (expects ~0.15.0); update the "zone.js" entry in
package.json (near the other Angular deps like "`@angular/core`",
"`@angular/common`") to "~0.15.0" or remove the explicit "zone.js" pin so npm/yarn
can resolve a compatible ~0.15.x version to satisfy the Angular peer dependency.
| }, | ||
| "dependencies": { | ||
| "@js-temporal/polyfill": "^0.4.4", | ||
| "@js-temporal/polyfill": "^0.5.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
What are the breaking changes in @js-temporal/polyfill version 0.5.0 compared to 0.4.4?
💡 Result:
Breaking changes in @js-temporal/polyfill v0.5.0 (vs v0.4.4), per the project changelog: 1) Temporal.ZonedDateTime removed as Intl.DateTimeFormat inputs - v0.5.0 removes support for passing Temporal.ZonedDateTime objects as parameters to Intl.DateTimeFormat formatting methods. Format instead via Temporal.ZonedDateTime.prototype.toLocaleString, which internally creates an Intl.DateTimeFormat for the same time zone/calendar and formats a Temporal.Instant created from the ZonedDateTime. Also: if you need a different time zone, create a new ZonedDateTime via withTimeZone (and include timeZone when creating Intl.DateTimeFormat). [1] 2) Temporal.ZonedDateTime time zone API changes -.timeZone on Temporal.ZonedDateTime is replaced with.timeZoneId (string) plus a.getTimeZone method returning an object implementing Temporal.TimeZoneProtocol. Termporal.Now.timeZone is replaced by Temporal.Now.timeZoneId. Time zones compare by string equality for calendar identifiers, and if the calendar is an object, its id is used. [1] 3) @js-temporal/polyfill v0.5.0: many convenience APIs removed (migration to alternative Temporal methods) - Removed getISOFields; use withCalendar('iso8601') and individual property getters. [2] - Removed withPlainDate; use with({ year, monthCode, day }). [2] - Removed Temporal.PlainTime.prototype.toPlainDateTime and toZonedDateTime; use same-named methods on Temporal.PlainDate to combine date+time. [2] - Removed epochSeconds and epochMicroseconds properties; compute from epochMilliseconds/epochNanoseconds as described in the changelog. [2] - Removed Temporal.Instant.fromEpochSeconds; use Temporal.Instant.fromEpochMilliseconds(epochSeconds * 1000). [2] - Removed Temporal.Instant.fromEpochMicroseconds; use Temporal.Instant.fromEpochNanoseconds(epochMicroseconds * 1000). [2] - Removed toPlainYearMonth and toPlainMonthDay on Temporal.PlainDateTime and Temporal.ZonedDateTime; use toPlainDate, then call the corresponding methods. [2] - Removed Temporal.Instant.prototype.toZonedDateTime and Temporal.Now.zonedDateTime; use toZonedDateTimeISO/zonedDateTimeISO and then withCalendar if needed. [2] 4) Temporal.Duration.prototype.add/subtract signature change - The relativeTo parameter is no longer accepted in Temporal.Duration.prototype.add and subtract. Instead: take a relativeTo object, add the two durations to it, and difference it with the original using until. [2] 5) Offset time zones precision restriction - Offset time zones are limited to minutes precision (e.g., [+01:01] allowed, but [+01:00:01] or [+01:00:00.000000001] not). [2] 6) Calendar/timezone customization removals (user-defined calendars and user-defined time zones) - User-defined calendars have been removed. [3] - User-defined time zones have been removed. [3] 7) Intl.DateTimeFormat formatting performance/memoization guidance (as part of migration notes) - Changelog emphasizes that Intl.DateTimeFormat instances are expensive and may need caching; also warns about system time zone changes during program lifetime. (This is part of the migration guidance around the ZonedDateTime/Intl breaking change.) [1] If you want, paste the specific code patterns you use from v0.4.4 (e.g., any Intl.DateTimeFormat.format(...) calls with ZonedDateTime, use of.timeZone / Temporal.Now.timeZone, or any removed convenience methods) and I’ll map each to the v0.5.0 replacements.
Citations:
- 1: https://github.com/js-temporal/temporal-polyfill/blob/73ed89bdd9ecbc553972f030df3a1114d898c18a/CHANGELOG.md
- 2: https://github.com/js-temporal/temporal-polyfill/blob/main/CHANGELOG.md
- 3: fix(deps): update dependency @js-temporal/polyfill to ^0.5.0 trpc/trpc#6643
Temporal polyfill 0.5.0 contains breaking API changes—audit usage.
The bump to @js-temporal/polyfill ^0.5.1 includes breaking changes from v0.4.4 to v0.5.0, including: Temporal.ZonedDateTime → Intl.DateTimeFormat interop changes (formatters no longer accept Temporal.ZonedDateTime inputs), .timeZone replaced by .timeZoneId (and Temporal.Now.timeZone replaced by Temporal.Now.timeZoneId), removal of multiple convenience APIs (e.g., getISOFields, withPlainDate, withPlainDateTime/conversion helpers, epochSeconds/epochMicroseconds, Instant.fromEpochSeconds/fromEpochMicroseconds, etc.), Temporal.Duration.prototype.add/subtract signature change (drops the relativeTo parameter), and stricter offset time zone precision. Audit integrations/react-next-15 for any of these APIs and update call sites to the v0.5.0 equivalents.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@integrations/react-next-15/package.json` at line 9, The package.json bump to
"`@js-temporal/polyfill`" ^0.5.1 introduces breaking API changes; audit the
integrations/react-next-15 code for any Temporal APIs and update call sites:
replace uses of Temporal.ZonedDateTime where passed to Intl.DateTimeFormat by
converting to compatible types or formatting strings, change all .timeZone and
Temporal.Now.timeZone to .timeZoneId, replace removed helpers like getISOFields,
withPlainDate, withPlainDateTime, Instant.fromEpochSeconds/fromEpochMicroseconds
and epochSeconds/epochMicroseconds with the new equivalent constructors and
conversion routines, update Duration.prototype.add/subtract call sites to the
new signatures (remove relativeTo parameter), and review any code relying on
looser zone offset precision; update imports/usages and tests accordingly to the
v0.5.0 API.
| "@tanstack/svelte-query": "workspace:*", | ||
| "@tanstack/svelte-query-devtools": "workspace:*", | ||
| "svelte": "^5.39.3", | ||
| "svelte": "^5.55.9", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
What are the notable changes and potential breaking changes in Svelte 5.40 through 5.55?
💡 Result:
Notable changes / potential breaking changes in Svelte 5.40 through 5.55 (inclusive), based on Svelte’s official release notes/changelog. I’m listing items that could require code/config review; most releases are bugfixes (low breaking risk). 1) 5.40.0 - Added createContext utility for type-safe context usage. This is additive (likely no breaking), but if you previously rolled your own helper you may want to migrate. [1] 2) 5.40.1 - “Remove sync-in-async warning for server rendering.” This is behavior/diagnostics-related (shouldn’t break runtime, but may change dev/test expectations). [1] 3) 5.40.2 - “Add hydration markers in pending branch of SSR boundary.” This affects SSR hydration markers and could fix/alter hydration behavior around async boundaries; if you have custom SSR/hydration tooling, review. [2] 4) 5.41.0 - Added $state.eager(value) rune. Additive, but if you rely on runes semantics/scheduling, review new rune usage patterns. [3] 5) 5.41.1 - “place let: declarations before {@const} declarations” (compiler/transform behavior change). This can be breaking if code previously relied on the old ordering being accepted. [4] 6) 5.41.1 - “improve each_key_without_as error” and “error if each block has key but no as clause.” This is primarily stricter/clearer compile-time validation; it may surface new compile errors in previously “wrong but tolerated” code. [3] 7) 5.52.0 - Added support for TrustedHTML in {@html} expressions. Additive, but if you were using Trusted Types / libraries, you may need to adjust types or usage to take advantage of the new path. [5] - “repair dynamic component truthy/falsy hydration mismatches” (SSR hydration behavior fix). If you had workarounds for hydration mismatch issues, review. [5] 8) 5.53.0 - “feat: allow comments in tags” (template grammar/parse). This is generally additive, but if you have unusual HTML-in-Svelte edge cases, validate parsing remains what you expect. [6] - “feat: allow error boundaries to work on the server” (SSR capability change). Additive, but review if you have custom error handling assumptions in SSR. [6] - “chore: deactivate current_batch by default in unset_context” (runtime/reactivity scheduling change). Potentially breaking if you rely on subtle batch/current_batch semantics around unset_context. [6] 9) 5.53.5 (representative in the 5.53 train) - Security-related fixes: “escape innerText and textContent bindings of contenteditable” and “sanitize transformError values prior to embedding in HTML comments.” Usually not breaking for correct code; could change rendered/sanitized output if you depended on raw/unescaped content. [7] 10) 5.54.0 - “allow css, runes, customElement compiler options to be functions” (compiler options API expansion). Potential breaking only if you had tooling that assumed these options are always non-callable literals/strings/booleans. [8] 11) 5.55.0 - Motion exports: now exports TweenOptions, SpringOptions, SpringUpdateOptions and Updater from svelte/motion. Additive (import path/types improvements). [9] 12) 5.55.1 - Patch fixes around server bindings and hydration for async {@html ...}. Likely bugfixes, but can affect hydration error behavior; review if you have custom hydration logic/tests. [10] 13) 5.55.5 and 5.55.6 (patches) - 5.55.5: “fix: don’t mark deriveds while an effect is updating” and “do not dispatch introstart event with animation of animate directive.” Typically bugfixes; could affect UI/event ordering or derived evaluation timing. [11] - 5.55.6: SSR/async correctness fixes such as “leave stale promises to wait for a later resolution” and “keep dependencies of $state.eager/pending …”. If you use $state.eager/pending, review semantics/timing changes (mostly correctness). [12] Bottom line: Most “notable” items across 5.40–5.55 are additive features (e.g., createContext, $state.eager, TrustedHTML support) or bugfixes (mostly SSR hydration and scheduling correctness). The only clearly potentially breaking items from the sources above are compiler strictness / ordering changes (e.g., let: before {@const}; each key requires as) and the unset_context batching semantic change—these can cause compile-time failures or subtle runtime behavior differences. [4][3][6]
Citations:
- 1: https://github.com/sveltejs/svelte/blob/HEAD/packages/svelte/CHANGELOG.md
- 2: Bump svelte from 5.38.7 to 5.41.1 humanspeak/svelte-satori-fix#35
- 3: https://github.com/sveltejs/svelte/releases/tag/svelte%405.41.0
- 4: https://github.com/sveltejs/svelte/blob/fcaa8ce7/packages/svelte/CHANGELOG.md
- 5: https://github.com/sveltejs/svelte/releases/tag/svelte%405.52.0
- 6: sveltejs/svelte@c2fc95a
- 7: sveltejs/svelte@ed14b49
- 8: https://github.com/sveltejs/svelte/releases/tag/svelte%405.54.0
- 9: https://github.com/sveltejs/svelte/releases/tag/svelte%405.55.0
- 10: https://github.com/sveltejs/svelte/releases/tag/svelte%405.55.1
- 11: https://github.com/sveltejs/svelte/releases/tag/svelte%405.55.5
- 12: https://github.com/sveltejs/svelte/releases/tag/svelte%405.55.6
Verify Svelte 5.39 → 5.55 compatibility.
Upgrading ^5.39.3 → ^5.55.9 (Svelte 5.40–5.55) is mostly additive + bugfixes, but there are a few places that can still break builds or behavior:
- Compiler strictness/ordering:
let:must come before{@const}, andeachblocks usingkeynow require anasclause (new compile errors possible). - Runtime semantics:
unset_contextbatching/current_batch behavior changed (can affect subtle update timing). - SSR/hydration behavior: hydration marker/mismatch fixes and server-capable error boundaries (review SSR/hydration-related tests/custom logic).
- Security/sanitization: contenteditable binding escaping/sanitization and
transformErrorHTML-comment embedding changes can affect output.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@integrations/svelte-vite/package.json` at line 12, The Svelte upgrade in
package.json (the "svelte" version bump to ^5.55.9) can introduce breaking
compiler/runtime/SSR changes; verify compatibility by running the repo's test
suite and QA flows and fix code where needed: ensure any component templates
place let: before {`@const`} and update all {`#each` ... key} blocks to include the
required "as" clause, inspect usages of unset_context/current_batch to account
for changed batching semantics, review SSR/hydration code and tests for
hydration marker changes and error-boundary behavior, and audit contenteditable
bindings and any transformError usage for sanitization/HTML-comment embedding
differences, adjusting components or test expectations accordingly.
| "vite-plugin-dts": "4.5.4", | ||
| "vite-plugin-externalize-deps": "^0.10.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
What changed in vite-plugin-externalize-deps version 0.10.0 compared to 0.9.0?
💡 Result:
Version 0.10.0 of vite-plugin-externalize-deps changed compared to 0.9.0 mainly in its dependency compatibility: it adds support for Vite 7 by updating dependencies and adding Vite 7 as a peer dependency, and the release was published on Oct 4, 2025, while 0.9.0 was published on Jan 19, 2025.[1][2][3] What exactly is different (as evidenced in the repo/release notes): - 0.10.0 updates the package to work with Vite 7 (“Allow Vite v7”).[3] - The PR that went into 0.10.0 is explicitly titled “chore(deps): update dependencies & support vite v7 as peer dependency” and states it updates deps and adds vite v7 as a peerDependency; it was merged on Oct 4, 2025 and notes “Released in v0.10.0”.[2] No other user-facing behavioral changes are clearly listed in the sources found (the official GitHub releases page snippets primarily mention Vite v7 / dependency updates for 0.10.0, and 0.9.0’s snippet we found is dependency update + adding vite v6 as a peer dependency).[4] Sources: - Version publication dates and version history for 0.10.0 vs 0.9.0.[5] - GitHub release/repo evidence for Vite v7 peer dependency in v0.10.0.[2][3]
Citations:
- 1: https://www.npmjs.com/package/vite-plugin-externalize-deps
- 2: chore(deps): update dependencies & support vite v7 as peer dependency davidmyersdev/vite-plugin-externalize-deps#11
- 3: https://github.com/davidmyersdev/vite-plugin-externalize-deps/releases
- 4: Update Dependencies, especially vite v6 davidmyersdev/vite-plugin-externalize-deps#9
- 5: https://registry.npmjs.org/vite-plugin-externalize-deps
🏁 Script executed:
#!/bin/bash
set -euo pipefail
rg -n "vite-plugin-externalize-deps" -S . || true
echo "----"
# Try common lockfiles
for f in pnpm-lock.yaml package-lock.json yarn.lock package-lock.yml; do
if [ -f "$f" ]; then
echo "== $f =="
rg -n "vite-plugin-externalize-deps" "$f" || true
fi
done
echo "----"
# Show the relevant package.json lines in question
if [ -f "packages/angular-query-experimental/package.json" ]; then
sed -n '80,130p' packages/angular-query-experimental/package.json | nl -ba | sed -n '1,120p'
fi
echo "----"
# Find where the plugin is used/configured (Vite config)
fd -t f "vite.config.*" . || true
fd -t f "vite.*config.*" packages || true
rg -n "externalize-deps" -S packages . || trueRepository: TanStack/query
Length of output: 1723
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== Versions in pnpm-lock.yaml (angular-query-experimental context) =="
rg -n "vite-plugin-externalize-deps@0\.(10|9)\.0" pnpm-lock.yaml || true
echo "== Plugin declaration in package.json =="
sed -n '80,120p' packages/angular-query-experimental/package.json
echo "== Vite config usage =="
sed -n '1,220p' packages/angular-query-experimental/vite.config.ts
echo "== Other references to externalizeDeps in this package =="
rg -n "externalizeDeps" packages/angular-query-experimental -S || true
echo "== Vite config files that mention vite-plugin-externalize-deps =="
rg -n "vite-plugin-externalize-deps" packages -S || trueRepository: TanStack/query
Length of output: 5454
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== Where externalDeps option is passed (angular-query-experimental) =="
rg -n "externalDeps" packages/angular-query-experimental -S || true
echo "== Check Options type usage (tanstack vite config) =="
rg -n "type Options|interface Options|externalDeps" packages -S --glob='*.ts' || trueRepository: TanStack/query
Length of output: 527
🌐 Web query:
vite-plugin-externalize-deps 0.10.0 changelog behavior include exclude default
💡 Result:
For vite-plugin-externalize-deps v0.10.0, the behavior is controlled by an except option (not a separate include/exclude pair): 1) Default behavior (what gets externalized) - deps: true - devDeps: false - peerDeps: true - optionalDeps: true - nodeBuiltins: true - except: [] (no exceptions by default) - It also uses useFile: join(process.cwd(), 'package.json') as the source of dependency lists [1][2][3]. So by default it externalizes runtime dependencies (and peer/optional deps, plus node built-ins), but not devDependencies; and it has no “excluded-by-default” list because except defaults to an empty array [1][2]. 2) “exclude” vs “except” vs “include” - The plugin’s config uses except to “include back” specific dependencies in your bundle (i.e., they will not be externalized) by providing exceptions [1][3]. - The README examples show except entries can be exact strings or regex patterns [1][3]. - There is no documented exclude or include option in the configuration snippet for v0.10.0; overriding is done by passing an object to externalizeDeps, whose defaults are shown (including except: []) [1][3]. 3) Changelog note on v0.10.0 specifically - I did not find (in the sources retrieved here) the actual v0.10.0 changelog entry(s) describing any behavioral change to include/exclude/except defaults. The sources available confirm the package version and defaults, but not a changelog section explaining the include/exclude default behavior [1][2][3]. If you share a link or paste the v0.10.0 changelog section you’re referring to, I can map it precisely to the current config options.
Citations:
- 1: https://www.npmjs.com/package/vite-plugin-externalize-deps
- 2: https://registry.npmjs.org/vite-plugin-externalize-deps
- 3: https://github.com/davidmyersdev/vite-plugin-externalize-deps
🌐 Web query:
vite-plugin-externalize-deps externalizeDeps options include except v0.10.0
💡 Result:
In vite-plugin-externalize-deps, the option is called except (not include) and it’s an “exception” list used to include specific dependencies in your bundle (i.e., do not externalize them). The plugin’s README and npm docs show except as the way to override what gets externalized, and they also show the default config shape. Example: externalizeDeps({ except: [ '@some/obscure/dependency', /^@some/obscure(?:/.+)?$/, ], }) For v0.10.0 specifically: the package exists and v0.10.0 was published on Oct 4, 2025, but the sources returned here do not show any separate/changed “include” option for v0.10.0. The documented behavior for controlling externalization still uses except. [1][2][3] So, for your query “externalizeDeps options include except v0.10.0”: 1) “except” is the supported option for including exceptions (keeping those dependencies bundled). [1][2] 2) I did not find evidence of an “include” option under externalizeDeps in the official README/docs for this package; “include” appears in unrelated projects/config concepts from other sources, not as this plugin’s externalizeDeps option. [1][2][3]
Citations:
- 1: https://registry.npmjs.org/vite-plugin-externalize-deps
- 2: https://www.npmjs.com/package/vite-plugin-externalize-deps
- 3: https://github.com/davidmyersdev/vite-plugin-externalize-deps
🌐 Web query:
vite-plugin-externalize-deps v0.9.0 options defaults deps peerDeps except
💡 Result:
For vite-plugin-externalize-deps v0.9.0, the default options for externalizeDeps are: - deps: true - devDeps: false - except: [] - nodeBuiltins: true - optionalDeps: true - peerDeps: true - useFile: join(process.cwd, 'package.json') [1] How “except” works in defaults: - The plugin externalizes dependencies by default (deps/devDeps/optionalDeps/peerDeps/nodeBuiltins), and you can prevent specific dependencies from being externalized by listing them in except (exact strings or regex patterns). The default is an empty array, meaning nothing is excepted. [1]
Citations:
🌐 Web query:
vite-plugin-externalize-deps v0.10.0 changelog externalization behavior except deps
💡 Result:
For vite-plugin-externalize-deps v0.10.0, the plugin’s externalization behavior is configured via externalizeDeps. By default it externalizes package dependencies (and peer/optional deps per flags), and you can prevent externalization for specific packages using the except option. Default “what gets externalized” - The documented default configuration is deps: true, devDeps: false, peerDeps: true, optionalDeps: true (and nodeBuiltins: true). [1] “Except deps” / exceptions behavior - The README states you can “include specific dependencies in your bundle” using except. [2] - It also shows except can match exact dependency names (strings) or dependency name patterns (RegExp). [2] v0.10.0 changelog note - v0.10.0 is listed as published on Oct 4, 2025. [3] - The specific v0.10.0 release-note text wasn’t captured in the snippets retrieved here; if you share the exact wording (or the release-note section you mean), I can map it precisely to the above runtime rules.
Citations:
- 1: https://github.com/davidmyersdev/vite-plugin-externalize-deps/blob/main/README.md
- 2: https://github.com/davidmyersdev/vite-plugin-externalize-deps
- 3: https://www.npmjs.com/package/vite-plugin-externalize-deps
🌐 Web query:
vite-plugin-externalize-deps externalizeDeps include option
💡 Result:
For vite-plugin-externalize-deps (package: "vite-plugin-externalize-deps" by davidmyersdev), there is no include option. Instead, the plugin has an except option that lets you “include specific dependencies in your bundle” by excluding them from being externalized. The README explicitly states: “To include specific dependencies in your bundle, you can add exceptions with the except option.”[1] Example usage: externalizeDeps({ except: [ '@some/obscure/dependency', /^@some/obscure(?:/.+)?$/, ], })[1] The documented default config object also lists except: [] (and does not list any include).[1][2]
Citations:
- 1: https://github.com/davidmyersdev/vite-plugin-externalize-deps/blob/main/README.md
- 2: https://registry.npmjs.org/vite-plugin-externalize-deps
🌐 Web query:
site:github.com davidmyersdev vite-plugin-externalize-deps include: externalizeDeps
💡 Result:
In davidmyersdev/vite-plugin-externalize-deps, the option called include:... is not part of the currently documented configuration API. Instead, the plugin exposes an except: [...] option to control what gets externalized. The README shows default config keys including deps, devDeps, except, nodeBuiltins, optionalDeps, peerDeps, and useFile, and it demonstrates using except to exclude certain dependencies from being externalized (i.e., you “include” specific deps by excluding others). [1] A separate GitHub release note snippet mentions an include option, but it is not reflected in the README’s configuration example for the plugin’s externalizeDeps(...) call. [2] Example using the documented option (except): externalizeDeps({ except: [ '@some/obscure/dependency', /^@some/obscure(?:/.+)?$/, ], }) [1]
Citations:
- 1: https://github.com/davidmyersdev/vite-plugin-externalize-deps/blob/main/README.md
- 2: https://github.com/davidmyersdev/vite-plugin-externalize-deps/releases
🌐 Web query:
vite-plugin-externalize-deps README except include options externalizeDeps
💡 Result:
To include (i.e., NOT externalize) specific dependencies with vite-plugin-externalize-deps, use the except option in the externalizeDeps configuration. Example: externalizeDeps({ except: [ // Match exact dependency names '@some/obscure/dependency', // Or match patterns with regular expressions /^@some/obscure(?:/.+)?$/, ], }) [1] By default, except is an empty array ([]), meaning no dependencies are explicitly included. [1] What to include based on your README request (“README except include options externalizeDeps”): in this plugin’s README, the option for inclusion/exclusion behavior is called except (used to include specific dependencies in your bundle). [1]
Citations:
Re-check externalization behavior for vite-plugin-externalize-deps ^0.10.0
v0.10.0’s change appears focused on Vite 7 compatibility (deps/peer dependency updates) rather than documented externalization-logic changes, so the bump is probably low risk for output differences. However, this package configures the plugin with externalizeDeps({ include: options.externalDeps ?? [] }), while the plugin docs describe except (not include) as the option to control which dependencies stay bundled—so the current include key may be ignored/incorrect and should be aligned. [packages/angular-query-experimental/package.json: 99-100; packages/angular-query-experimental/vite.config.ts: ~68]
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/angular-query-experimental/package.json` around lines 99 - 100, The
plugin is being configured with externalizeDeps({ include: options.externalDeps
?? [] }) which likely uses the wrong option name and will be ignored by the
plugin; change the configuration in vite.config.ts to use the documented option
name (except) instead of include so you pass externalizeDeps({ except:
options.externalDeps ?? [] }) or otherwise map your options to the plugin's
expected API; verify the semantics (except lists deps that should remain
bundled) and keep the dependency version ("vite-plugin-externalize-deps":
"^0.10.0") as-is unless you need to pin for Vite compatibility.
4ed2a06 to
71691be
Compare
There was a problem hiding this comment.
♻️ Duplicate comments (2)
examples/angular/rxjs/package.json (1)
20-20:⚠️ Potential issue | 🟠 Major | ⚡ Quick win
zone.jsversion should be aligned with Angular 20 peers.Line 20 pins
zone.jsto0.16.2; with@angular/*@20.3.21``, this is likely outside the expected peer range. Prefer~0.15.0(or omit explicit pin).Proposed fix
- "zone.js": "0.16.2" + "zone.js": "~0.15.0"Verification command:
#!/bin/bash npm view `@angular/core`@20.3.21 peerDependencies --json | jq -r '."zone.js"'🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@examples/angular/rxjs/package.json` at line 20, The package.json currently pins "zone.js": "0.16.2" which doesn't match Angular 20 peer expectations; update the "zone.js" entry in examples/angular/rxjs/package.json to a compatible range (e.g., "~0.15.0") or remove the explicit pin so peers can resolve it, ensuring the change targets the "zone.js" key in the file and that package lock / install is refreshed afterwards.examples/angular/router/package.json (1)
20-20:⚠️ Potential issue | 🟠 Major | ⚡ Quick win
zone.jspin likely violates Angular 20 peer range.Line 20 pins
zone.jsto0.16.2, which is likely incompatible with@angular/core@20.3.21peer requirements. Please align to~0.15.0(or remove the explicit pin).Proposed fix
- "zone.js": "0.16.2" + "zone.js": "~0.15.0"Use this read-only check to confirm the exact peer range before merging:
#!/bin/bash npm view `@angular/core`@20.3.21 peerDependencies --json | jq -r '."zone.js"'🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@examples/angular/router/package.json` at line 20, The package.json dependency "zone.js" is pinned to "0.16.2" which likely violates `@angular/core`@20.3.21 peer requirements; update the "zone.js" entry in package.json (the dependency key "zone.js") to either remove the explicit pin or change its version to the compatible range "~0.15.0" (or whatever the npm view check returns) so it matches Angular's peerDependency for `@angular/core`.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Duplicate comments:
In `@examples/angular/router/package.json`:
- Line 20: The package.json dependency "zone.js" is pinned to "0.16.2" which
likely violates `@angular/core`@20.3.21 peer requirements; update the "zone.js"
entry in package.json (the dependency key "zone.js") to either remove the
explicit pin or change its version to the compatible range "~0.15.0" (or
whatever the npm view check returns) so it matches Angular's peerDependency for
`@angular/core`.
In `@examples/angular/rxjs/package.json`:
- Line 20: The package.json currently pins "zone.js": "0.16.2" which doesn't
match Angular 20 peer expectations; update the "zone.js" entry in
examples/angular/rxjs/package.json to a compatible range (e.g., "~0.15.0") or
remove the explicit pin so peers can resolve it, ensuring the change targets the
"zone.js" key in the file and that package lock / install is refreshed
afterwards.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: ccfdab30-8f2d-48b6-b237-2a28e4c824f2
📒 Files selected for processing (93)
.github/workflows/zizmor.ymlexamples/angular/auto-refetching/package.jsonexamples/angular/basic-persister/package.jsonexamples/angular/basic/package.jsonexamples/angular/devtools-panel/package.jsonexamples/angular/infinite-query-with-max-pages/package.jsonexamples/angular/optimistic-updates/package.jsonexamples/angular/pagination/package.jsonexamples/angular/query-options-from-a-service/package.jsonexamples/angular/router/package.jsonexamples/angular/rxjs/package.jsonexamples/angular/simple/package.jsonexamples/lit/basic/package.jsonexamples/lit/pagination/package.jsonexamples/lit/ssr/package.jsonexamples/preact/simple/package.jsonexamples/react/algolia/package.jsonexamples/react/basic-graphql-request/package.jsonexamples/react/basic/package.jsonexamples/react/chat/package.jsonexamples/react/default-query-function/package.jsonexamples/react/devtools-panel/package.jsonexamples/react/eslint-legacy/package.jsonexamples/react/eslint-plugin-demo/package.jsonexamples/react/offline/package.jsonexamples/react/playground/package.jsonexamples/react/react-native/package.jsonexamples/react/react-router/package.jsonexamples/react/rick-morty/package.jsonexamples/react/shadow-dom/package.jsonexamples/react/simple/package.jsonexamples/react/star-wars/package.jsonexamples/react/suspense/package.jsonexamples/solid/astro/package.jsonexamples/solid/basic-graphql-request/package.jsonexamples/solid/basic/package.jsonexamples/solid/default-query-function/package.jsonexamples/solid/offline/package.jsonexamples/solid/simple/package.jsonexamples/solid/solid-start-streaming/package.jsonexamples/svelte/auto-refetching/package.jsonexamples/svelte/basic/package.jsonexamples/svelte/load-more-infinite-scroll/package.jsonexamples/svelte/optimistic-updates/package.jsonexamples/svelte/playground/package.jsonexamples/svelte/simple/package.jsonexamples/svelte/ssr/package.jsonexamples/svelte/star-wars/package.jsonexamples/vue/2.6-basic/package.jsonexamples/vue/2.7-basic/package.jsonexamples/vue/basic/package.jsonexamples/vue/dependent-queries/package.jsonexamples/vue/nuxt3/package.jsonexamples/vue/persister/package.jsonexamples/vue/simple/package.jsonintegrations/angular-cli-20/package.jsonintegrations/lit-vite/package.jsonintegrations/react-next-15/package.jsonintegrations/react-next-16/package.jsonintegrations/react-vite/package.jsonintegrations/react-webpack-4/package.jsonintegrations/react-webpack-5/package.jsonintegrations/solid-vite/package.jsonintegrations/svelte-vite/package.jsonintegrations/vue-vite/package.jsonpackage.jsonpackages/angular-query-experimental/package.jsonpackages/angular-query-persist-client/package.jsonpackages/eslint-plugin-query/package.jsonpackages/lit-query/package.jsonpackages/preact-query-devtools/package.jsonpackages/preact-query-persist-client/package.jsonpackages/preact-query/package.jsonpackages/query-async-storage-persister/package.jsonpackages/query-broadcast-client-experimental/package.jsonpackages/query-core/package.jsonpackages/query-devtools/package.jsonpackages/query-persist-client-core/package.jsonpackages/query-sync-storage-persister/package.jsonpackages/query-test-utils/package.jsonpackages/react-query-devtools/package.jsonpackages/react-query-next-experimental/package.jsonpackages/react-query-persist-client/package.jsonpackages/react-query/package.jsonpackages/solid-query-devtools/package.jsonpackages/solid-query-persist-client/package.jsonpackages/solid-query/package.jsonpackages/svelte-query-devtools/package.jsonpackages/svelte-query-persist-client/package.jsonpackages/svelte-query/package.jsonpackages/vue-query-devtools/package.jsonpackages/vue-query/package.jsonpnpm-workspace.yaml
✅ Files skipped from review due to trivial changes (45)
- packages/query-test-utils/package.json
- packages/query-core/package.json
- packages/query-sync-storage-persister/package.json
- packages/query-persist-client-core/package.json
- examples/react/playground/package.json
- packages/react-query-next-experimental/package.json
- examples/lit/pagination/package.json
- packages/query-async-storage-persister/package.json
- packages/lit-query/package.json
- integrations/react-next-15/package.json
- packages/query-broadcast-client-experimental/package.json
- packages/solid-query/package.json
- examples/vue/persister/package.json
- examples/vue/simple/package.json
- examples/vue/2.6-basic/package.json
- examples/solid/default-query-function/package.json
- packages/react-query-persist-client/package.json
- examples/react/eslint-legacy/package.json
- packages/react-query-devtools/package.json
- packages/vue-query/package.json
- examples/solid/basic/package.json
- packages/svelte-query-devtools/package.json
- packages/solid-query-devtools/package.json
- examples/react/basic/package.json
- packages/preact-query-devtools/package.json
- packages/preact-query/package.json
- examples/svelte/optimistic-updates/package.json
- examples/solid/astro/package.json
- examples/svelte/playground/package.json
- integrations/react-next-16/package.json
- integrations/react-vite/package.json
- packages/svelte-query-persist-client/package.json
- examples/react/rick-morty/package.json
- integrations/vue-vite/package.json
- integrations/react-webpack-4/package.json
- examples/react/devtools-panel/package.json
- examples/svelte/auto-refetching/package.json
- examples/react/shadow-dom/package.json
- examples/lit/basic/package.json
- examples/angular/basic/package.json
- examples/react/default-query-function/package.json
- examples/solid/offline/package.json
- packages/solid-query-persist-client/package.json
- packages/preact-query-persist-client/package.json
- examples/angular/simple/package.json
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
fe05f29 to
bb78924
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
bb78924 to
5de1082
Compare
This PR contains the following updates:
5.2.1→5.52.1^20.0.0→^20.3.21^20.0.0→^20.3.26^20.0.0→^20.3.26^20.0.0→^20.3.21^20.0.0→^20.3.21^20.0.0→^20.3.21^20.0.0→^20.3.21^20.0.0→^20.3.21^20.0.0→^20.3.21^20.0.0→^20.3.21^20.0.0→^20.3.21^20.0.0→^20.3.21^20.0.0→^20.3.21^20.0.0→^20.3.21^0.15.3→^0.18.2^0.9.4→^0.9.9^5.0.7→^5.1.3^7.26.0→^7.29.7^7.24.9→^7.29.7^7.26.0→^7.29.7^7.25.9→^7.29.7^2.29.8→^2.31.0^9.2.1→^9.8.0^2.0.1→^2.13.0^9.36.0→^9.39.4^10.0.5→^10.0.11^0.4.4→^0.5.1^0.13.4→^0.13.11^3.3.0→^3.3.1^1.1.7→^1.1.8^2.10.2→^2.10.5^11.4.1→^11.5.2^12.0.0→^12.1.0^1.2.2→^1.5.3^2.0.26→^2.1.5^0.15.3→^0.16.1^1.1.3→^1.3.2^6.1.0→^6.1.1^2.57.1→^2.61.1^2.4.0→^2.5.7^4.1.13→^4.3.0^4.0.14→^4.3.00.3.2→0.4.00.3.1→0.3.30.4.3→0.5.2^5.90.2→^5.100.14^18.0.0→^18.1.1^10.4.0→^10.4.1^6.8.0→^6.9.1^16.1.0→^16.3.2^5.2.8→^5.3.1^5.0.4→^5.0.88.58.1→8.59.48.58.1→8.59.4^8.48.0→^8.59.48.58.1→8.59.48.58.1→8.59.4^8.48.0→^8.59.48.58.1→8.59.48.58.1→8.59.48.58.1→8.59.48.58.1→8.59.48.58.1→8.59.48.58.1→8.59.4^8.58.1→^8.59.48.58.1→8.59.4^4.3.4→^4.7.0^4.3.4→^4.7.0^5.2.1→^5.2.44.0.6→4.1.7^1.4.0→^1.6.18^6.6.3→^6.6.4^8.3.0→^8.4.1^7.0.0→^7.3.0^0.27.2→^0.28.0^9.36.0→^9.39.4^9.39.0→^9.39.4^50.5.0→^50.8.0^3.11.0→^3.17.1^10.5.0→^10.9.1^1.2.1→^1.2.2^52.0.11→^52.0.49^17.0.3→^17.1.8^2.0.0→^2.2.3^17.4.0→^17.6.0^2.1.16→^2.1.19^16.9.0→^16.14.0^7.1.2→^7.4.0^5.6.3→^5.6.7^6.2.1→^6.2.4^27.0.0→^27.4.0^6.0.2→^6.14.2^3.3.1→^3.3.3^4.0.2→^4.0.3^2.6.6→^2.14.6^5.0.0→^5.0.2^3.12.4→^3.21.622.1.3→22.7.311.1.0→11.3.0>=11.0.0→>=11.3.0^10.28.0→^10.29.2^10.28.0→^10.29.2^6.6.4→^6.7.0^3.7.4→^3.8.3^3.4.0→^3.5.2^0.3.13→^0.3.21^2.5.2→^2.6.0^0.76.3→^0.85.3^2.20.2→^2.31.2^5.12.5→^5.15.2^3.16.2→^3.19.5^4.12.0→^4.14.1^4.1.0→^4.25.2^0.19.13→^0.21.2^6.25.1→^6.30.3^6.25.1→^6.30.3^8.0.0→^8.4.0~7.8.0→~7.8.2^1.6.1→^1.11.1^12.0.0→^12.1.0^1.9.7→^1.9.13^1.9.7→^1.9.13^0.2.3→^0.3.0^2.2.2→^2.2.6