update

[isamu]

Summary by CodeRabbit

• Chores
  • Updated development and framework dependencies to latest patch versions across all packages for enhanced stability and security.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request updates dependency versions across the monorepo's package.json files. The root package.json, packages/grapys-vue/package.json, and packages/vueweave/package.json are bumped with minor version increments for development dependencies including Vue, TypeScript tooling, and build utilities.

Changes

Cohort / File(s)	Summary
Monorepo Dependency Updates package.json	Updated 4 dependencies: @types/react (^19.2.8 → ^19.2.9), prettier (^3.8.0 → ^3.8.1), typescript-eslint (^8.53.0 → ^8.53.1), @graphai/gemini_agent (^2.0.3 → ^2.0.4)
Vue Package Dependencies packages/grapys-vue/package.json	Bumped vue from ^3.5.26 to ^3.5.27
Vueweave Package Dependencies packages/vueweave/package.json	Updated 3 dependencies: @types/node (25.0.9 → 25.0.10), prettier (3.8.0 → 3.8.1), vue (3.5.26 → 3.5.27)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Hops of joy through dependency lanes,
Version bumps in the spring rains,
Prettier code, and Vue shines bright,
Dependencies dancing—all feels right! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'update' is vague and generic, failing to convey meaningful information about the changeset of dependency version bumps.	Use a more descriptive title like 'Update package dependencies' or 'Bump dependency versions across packages' to clearly communicate the nature of the changes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@packages/vueweave/package.json`:
- Around line 39-47: Update the `@types/node` dependency version in package.json
from "^25.0.10" to "^22.x" to align type definitions with the CI Node 22.x
target; locate the dependencies block containing the "@types/node" entry and
replace its version specifier so the package uses Node 22 typings.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

@types/node 25.0.10 Node.js version compatibility

💡 Result:

@types/node@25.0.10 targets Node.js v25 (the @types/node major number matches the Node major). Use it when your runtime/ambient Node APIs are Node 25; for earlier Node LTS (e.g. 24, 22, 20) prefer the corresponding @types/node major (24, 22, 20). [1][2]

Sources:

• DefinitelyTyped explanation of how @types/node versions map to Node.js major/minor. [1]
• @types/node release listings showing 25.x releases. [2]

---

🌐 Web query:

Prettier 3.8.1 release notes compatibility requirements

💡 Result:

Prettier 3.8.1 minimum compatibility (short):

• Node.js: requires Node >= 14. [1][2]
• ESLint/related: eslint-plugin/eslint-config integrations expect modern ESLint (>=8) and Prettier >=3 for peer-deps; use matching eslint-plugin-prettier / eslint-config-prettier versions. [1][3]

Sources:

• Prettier blog (3.8 release notes). [1]
• package metadata / lockfile excerpts showing Prettier's engines: "node": ">=14". [2]

References:
[1] https://prettier.io/blog/2026/01/14/3.8.0
[2] example package-lock/package metadata showing Prettier engines "node": ">=14". (see package-lock excerpts). [3] eslint-plugin-prettier README (peer/compat notes).

---

🌐 Web query:

Vue 3.5.27 release notes and compatibility

💡 Result:

Summary — Vue 3.5.27

• What it is: a patch release in the Vue 3.5 line (patch-level fixes/bugfixes). [1][2]
• Release date / latest tag: published Jan 19, 2026 (v3.5.27). [2]
• Notes: patch releases generally contain bug fixes and small improvements; full changelog/commit list is available on the Vue GitHub releases / CHANGELOG for the 3.5 minor. [1][2]

Compatibility

• No public API breaking changes are introduced by patch releases in the 3.x line; 3.5.27 is compatible with other 3.5.x runtime behavior. [1]
• Important cross-version caveat (still applies generally): code compiled by a newer template compiler may be incompatible with an older Vue runtime (i.e., ensure compiler/runtime versions align for pre-compiled components/libraries). Also check TypeScript minimums for typings if you rely on shipped declarations. [3][1]

Where to read the full notes

• Official changelog / GitHub releases (detailed commits and PRs for v3.5.x). [1]
• Vue blog / release announcement for the 3.5 minor (overview of features in 3.5). [3]
• End-of-life / version index confirming v3.5.27 as current patch (Jan 19, 2026). [2]

Sources
[1] Vue GitHub releases / CHANGELOG.
[2] endoflife.date — Vue (shows v3.5.27, 19 Jan 2026).
[3] Vue blog post announcing Vue 3.5 (overview and compatibility notes).

---

🏁 Script executed:

# Check if there's additional context in the repository about Node version targets
cd packages/vueweave 2>/dev/null && cat package.json | head -20

Repository: receptron/grapys

Length of output: 467

---

🏁 Script executed:

# Check for Node version specifications
if [ -f .nvmrc ]; then cat .nvmrc; fi
if [ -f .node-version ]; then cat .node-version; fi
if [ -f .github/workflows/*.yml ] || [ -f .github/workflows/*.yaml ]; then grep -r "node-version" .github/workflows/ 2>/dev/null | head -5; fi
# Check root package.json engines field
cat package.json | jq '.engines' 2>/dev/null || echo "No engines field in root package.json"

Repository: receptron/grapys

Length of output: 277

---

Use @types/node ^22.x to align with the Node 22.x CI target.

The project's CI pipeline targets Node 22.x, but @types/node ^25.0.10 targets Node 25 (major version alignment). This mismatch can cause type inconsistencies. Change to @types/node ^22.x to match your build target. Prettier 3.8.1 and Vue 3.5.27 are compatible with Node 22 and have no known issues.

🤖 Prompt for AI Agents

In `@packages/vueweave/package.json` around lines 39 - 47, Update the `@types/node`
dependency version in package.json from "^25.0.10" to "^22.x" to align type
definitions with the CI Node 22.x target; locate the dependencies block
containing the "@types/node" entry and replace its version specifier so the
package uses Node 22 typings.