You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
chore(deps): align 'catalog', 'vue' and 'next' dev ranges with examples after the security update - #12515
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
No actionable comments were generated in the recent review.
Walkthrough
The PR raises Vue version ranges in example and integration manifests and the workspace catalog. It also updates catalog ranges for React Vite and Solid packages, and raises the Next.js development dependency in react-query-next-experimental.
Vue ranges changed to ^3.5.44. The workspace catalog also updates @vitejs/plugin-react, solid-js, and vite-plugin-solid. The Next.js development dependency changed to ^16.4.4.
TanStack/query#12509: Updates related React, Solid, and Next.js dependency versions.
TanStack/query#12438: Adds Vue examples whose package manifests are updated here.
TanStack/query#12439: Adds Vue example manifests whose dependency ranges are updated here.
Suggested reviewers:damianosipiuk
Merge Risk: Minimal · up to 68ed4
The dependency-range alignment presents no identified merge-blocking risk and is mergeable subject to normal installation and test checks.
Pre-merge checks: 5
Check name
Status
Explanation
Title check
The title accurately summarizes the dependency-range alignment across the catalog, Vue examples, and Next development dependency. It is specific and related to the main changes.
Description check
The description includes the required Changes, Checklist, and Release Impact sections. It explains the dependency updates, reports testing, and marks the change as dev-only with no release impact.
Docstring Coverage
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (23 skipped: 23 unsupported.)
Finishing Touches
Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎯 Changes
Align the remaining dev dependency ranges with the versions now used in
examplesandintegrations.pnpm-workspace.yamlcatalog:solid-js^1.9.18,vite-plugin-solid^2.11.15,@vitejs/plugin-react^6.2.1andvue^3.5.44.vue:^3.5.43→^3.5.44in the examples and integrations that were not on it yet, matching the Nuxt examples and integrations.packages/react-query-next-experimental: dev dependencynext^16.0.1→^16.4.4.pnpm-lock.yaml. Only the specifiers change; the resolved versions stay the same.✅ Checklist
pnpm run test:pr, or these tests do not apply to this pull request.🚀 Release Impact
Summary by CodeRabbit