Dependencies update #69
Conversation
fix: update all dependencies
WalkthroughBumps package manager and dev dependencies, updates CHANGELOG date and link, adds minor formatting in CREDITS, and applies whitespace/indentation-only changes in source and test files. No functional logic, control flow, or public API alterations. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches
🧪 Generate unit tests
Tip 👮 Agentic pre-merge checks are now available in preview!Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.
Please see the documentation for more information. Example: reviews:
pre_merge_checks:
custom_checks:
- name: "Undocumented Breaking Changes"
mode: "warning"
instructions: |
Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).Please share your feedback with us on this Discord post. 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. 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
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (8)
CHANGELOG.md(2 hunks)CREDITS.md(4 hunks)package.json(2 hunks)src/index.ts(5 hunks)src/utilities.ts(2 hunks)test/components/ReadProvider.vue(1 hunks)test/components/RemoveProvider.vue(1 hunks)test/components/SubmitProvider.vue(1 hunks)
🧰 Additional context used
🧬 Code graph analysis (2)
src/index.ts (1)
src/types.ts (1)
StoreRepositoryHash(20-33)
src/utilities.ts (1)
src/types.ts (1)
ParamMap(4-7)
🔇 Additional comments (13)
test/components/ReadProvider.vue (1)
7-7: Formatting-only change is fine.No semantic/runtime impact.
test/components/RemoveProvider.vue (1)
7-7: Formatting-only change is fine.No semantic/runtime impact.
test/components/SubmitProvider.vue (1)
7-7: Formatting-only change is fine.No semantic/runtime impact.
CREDITS.md (1)
35-35: Whitespace tweak looks good.No content/license changes.
Also applies to: 67-67, 99-99, 131-131
src/index.ts (5)
137-143: No-op formatting around default storeHash init.Semantics unchanged.
330-337: Reduce/flag aggregation formatting only.Logic preserved.
505-509: Read: options unwrap linewrap only.All good.
727-739: Submit: conditional create/update formatting only.All good.
941-945: Remove: options unwrap formatting only.All good.
src/utilities.ts (4)
108-119: watchIgnorable debounce block — formatting only.Behavior unchanged.
125-136: watchIgnorable (executeWhen) — formatting only.Behavior unchanged.
225-236: Submit auto-execute watcher — formatting only.Behavior unchanged.
243-253: Submit executeWhen watcher — formatting only.Behavior unchanged.
| All notable changes to this project will be documented in this file. | ||
|
|
||
| ## [2.0.1] - 2025-06-18 | ||
| ## [2.0.1] - 2025-09-16 |
There was a problem hiding this comment.
🧩 Analysis chain
Verify tag/date alignment for 2.0.1.
Ensure the 2025-09-16 date and compare link match an existing tag/release on GitHub.
Run:
Also applies to: 98-98
🏁 Script executed:
#!/bin/bash
# Check release/tag exists and created date
gh api repos/volverjs/query-vue/releases/tags/v2.0.1 --jq '{tag_name, created_at, published_at, html_url}' || echo "No release for v2.0.1"
gh api repos/volverjs/query-vue/tags --jq '.[]|select(.name=="v2.0.1")' || echo "No tag v2.0.1"Length of output: 179
CHANGELOG: v2.0.1 entry references a missing GitHub tag/release
gh API returned 404 — no release or tag named v2.0.1 found in repos/volverjs/query-vue; update CHANGELOG.md or create the v2.0.1 tag/release so the 2025-09-16 date/compare link is accurate.
Location: CHANGELOG.md — line 5 (## [2.0.1] - 2025-09-16) and also applies to line 98.
🤖 Prompt for AI Agents
In CHANGELOG.md around lines 5 and 98, the release header "## [2.0.1] -
2025-09-16" references a non-existent GitHub tag/release (gh API returned 404);
either create and push a Git tag/release named v2.0.1 in the
repos/volverjs/query-vue repository or update the CHANGELOG.md entry to
reference the correct existing tag/release (or remove the link/compare URL and
adjust the date) so the header and any compare links are accurate.
| "type": "module", | ||
| "version": "0.0.0", | ||
| "packageManager": "pnpm@10.13.1", | ||
| "packageManager": "pnpm@10.16.1", |
There was a problem hiding this comment.
pnpm 10 requires Node ≥18.12 — engines currently allow Node 16.
This can break local dev/CI when Corepack enforces pnpm@10.16.1 on Node 16. Raise Node engine or pin pnpm lower.
Update engines to reflect toolchain support:
"engines": {
- "node": ">= 16.x"
+ "node": "^20.19.0 || >=22.12.0",
+ "pnpm": ">=10"
},Refs: pnpm 10 needs Node ≥18.12; Vite 7 needs Node 20.19+ or 22.12+. (pnpm.io)
Committable suggestion skipped: line range outside the PR's diff.
🤖 Prompt for AI Agents
In package.json around line 5, the packageManager is set to "pnpm@10.16.1" but
the engines.allow Node 16 which is incompatible with pnpm v10; update the
package.json engines.node to a Node version that meets toolchain requirements
(e.g. ">=18.12.0" to satisfy pnpm 10, or ">=20.19.0" / ">=22.12.0" if you must
satisfy Vite 7) or alternatively pin packageManager to a pnpm v9/v8 release;
choose one approach, then update the engines field accordingly (or downgrade the
packageManager entry) so Corepack/pnpm enforcement won't break CI/local dev.
| "@antfu/eslint-config": "^5.3.0", | ||
| "@nabla/vite-plugin-eslint": "^2.0.6", | ||
| "@pinia/testing": "^1.0.2", | ||
| "@types/node": "^24.1.0", | ||
| "@types/node": "^24.5.0", | ||
| "@vitejs/plugin-vue": "^6.0.1", | ||
| "@volverjs/data": "^2.0.2", | ||
| "@volverjs/data": "^2.0.3", | ||
| "@vue/test-utils": "^2.4.6", | ||
| "@vueuse/core": "^13.5.0", | ||
| "@vueuse/core": "^13.9.0", | ||
| "copy": "^0.3.2", | ||
| "eslint": "^9.32.0", | ||
| "eslint": "^9.35.0", | ||
| "happy-dom": "^18.0.1", | ||
| "pinia": "^3.0.3", | ||
| "typescript": "5.9.2", | ||
| "vite": "^7.0.6", | ||
| "vite": "^7.1.5", | ||
| "vite-plugin-dts": "^4.5.4", | ||
| "vitest": "^3.2.4", | ||
| "vitest-fetch-mock": "^0.4.5", | ||
| "vue": "^3.5.18", | ||
| "vue-tsc": "^3.0.4" | ||
| "vue": "^3.5.21", | ||
| "vue-tsc": "^3.0.7" | ||
| }, |
There was a problem hiding this comment.
Vite 7 in devDependencies implies Node 20.19+; align engines accordingly.
Current engines field (Node ≥16) is incompatible with Vite 7’s requirements and may cause installs/builds to fail in Node 16/18 environments.
Apply the engines update above; optionally document the Node upgrade in README/CONTRIBUTING.
Refs: Vite 7 requires Node 20.19+ or 22.12+. (vite.dev)
🤖 Prompt for AI Agents
In package.json around lines 67 to 86 the devDependencies include Vite 7 which
requires Node >=20.19 (or 22.12+), but the engines field currently allows Node
≥16; update the engines.node entry in package.json to explicitly require Node
>=20.19.0 (or a range such as ">=20.19.0 || >=22.12.0") so installs/builds fail
fast on unsupported Node versions, and update any
CI/workflow/README/CONTRIBUTING references to document the Node upgrade
requirement.
fix: update all dependencies
Summary by CodeRabbit
Documentation
Chores
Style
Tests