chore(deps-dev): bump the dev-dependencies group across 1 directory with 7 updates#114
chore(deps-dev): bump the dev-dependencies group across 1 directory with 7 updates#114dependabot[bot] wants to merge 1 commit into
Conversation
…ith 7 updates Bumps the dev-dependencies group with 7 updates in the / directory: | Package | From | To | | --- | --- | --- | | [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `22.19.19` | `25.7.0` | | [lint-staged](https://github.com/lint-staged/lint-staged) | `16.4.0` | `17.0.4` | | [typescript](https://github.com/microsoft/TypeScript) | `5.9.3` | `6.0.3` | | [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react) | `4.7.0` | `6.0.1` | | [jsdom](https://github.com/jsdom/jsdom) | `26.1.0` | `29.1.1` | | [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `6.4.2` | `8.0.12` | | [dotenv](https://github.com/motdotla/dotenv) | `16.6.1` | `17.4.2` | Updates `@types/node` from 22.19.19 to 25.7.0 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) Updates `lint-staged` from 16.4.0 to 17.0.4 - [Release notes](https://github.com/lint-staged/lint-staged/releases) - [Changelog](https://github.com/lint-staged/lint-staged/blob/main/CHANGELOG.md) - [Commits](lint-staged/lint-staged@v16.4.0...v17.0.4) Updates `typescript` from 5.9.3 to 6.0.3 - [Release notes](https://github.com/microsoft/TypeScript/releases) - [Commits](microsoft/TypeScript@v5.9.3...v6.0.3) Updates `@vitejs/plugin-react` from 4.7.0 to 6.0.1 - [Release notes](https://github.com/vitejs/vite-plugin-react/releases) - [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite-plugin-react/commits/[email protected]/packages/plugin-react) Updates `jsdom` from 26.1.0 to 29.1.1 - [Release notes](https://github.com/jsdom/jsdom/releases) - [Commits](jsdom/jsdom@v26.1.0...v29.1.1) Updates `vite` from 6.4.2 to 8.0.12 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v8.0.12/packages/vite) Updates `dotenv` from 16.6.1 to 17.4.2 - [Changelog](https://github.com/motdotla/dotenv/blob/master/CHANGELOG.md) - [Commits](motdotla/dotenv@v16.6.1...v17.4.2) --- updated-dependencies: - dependency-name: "@types/node" dependency-version: 25.7.0 dependency-type: direct:development update-type: version-update:semver-major dependency-group: dev-dependencies - dependency-name: lint-staged dependency-version: 17.0.4 dependency-type: direct:development update-type: version-update:semver-major dependency-group: dev-dependencies - dependency-name: typescript dependency-version: 6.0.3 dependency-type: direct:development update-type: version-update:semver-major dependency-group: dev-dependencies - dependency-name: "@vitejs/plugin-react" dependency-version: 6.0.1 dependency-type: direct:development update-type: version-update:semver-major dependency-group: dev-dependencies - dependency-name: jsdom dependency-version: 29.1.1 dependency-type: direct:development update-type: version-update:semver-major dependency-group: dev-dependencies - dependency-name: vite dependency-version: 8.0.12 dependency-type: direct:development update-type: version-update:semver-major dependency-group: dev-dependencies - dependency-name: dotenv dependency-version: 17.4.2 dependency-type: direct:development update-type: version-update:semver-major dependency-group: dev-dependencies ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
Bot
added
dependencies
📝 WalkthroughWalkthroughTypeScript is upgraded to 6.0.3 across all packages in the monorepo. The root package.json adds upgrades for ChangesMonorepo Dependency Upgrades
🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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: 2
🤖 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 `@apps/desktop/package.json`:
- Around line 42-46: package.json lists upgraded majors for vite,
`@vitejs/plugin-react`, jsdom and typescript that conflict with the current
bun.lock pins ([email protected], `@vitejs/plugin-react`@^4, [email protected]); regenerate
the lockfile so bun.lock matches package.json by removing or regenerating
bun.lock and running a fresh lockfile install (e.g., bun install) to produce a
new bun.lock that resolves vite ^8, `@vitejs/plugin-react` ^6, jsdom ^29 and
typescript ^6.0, then verify vite.config.ts and vitest.config.ts still work and
commit the updated bun.lock together with package.json.
In `@apps/website/package.json`:
- Line 24: package.json currently pins "typescript": "^6.0.3" but the project’s
Next.js version is incompatible; update package.json to either bump Next.js to
^16.2.0 or later (modify the "next" dependency) to ensure TypeScript 6 support,
run a fresh install and test, or alternatively change the "typescript" entry to
"^5.1.0" to match the existing Next.js version; ensure you update the same
package.json that contains the "typescript" field and run the lockfile update
(npm/yarn/pnpm install) and CI to validate the toolchain.
🪄 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: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 82b01d20-3760-42cd-a34f-a8afb9df3651
📒 Files selected for processing (14)
apps/dashboard/package.jsonapps/desktop/package.jsonapps/website/package.jsonpackage.jsonpackages/agent-definitions/package.jsonpackages/cli/package.jsonpackages/database/package.jsonpackages/github-action/package.jsonpackages/installer/package.jsonpackages/mcp-server/package.jsonpackages/shared/package.jsonpackages/storage/package.jsonpackages/ui-utils/package.jsonpackages/ui/package.json
| "@vitejs/plugin-react": "^6", | ||
| "jsdom": "^29", | ||
| "tailwindcss": "^4", | ||
| "typescript": "^5.9", | ||
| "vite": "^6", | ||
| "typescript": "^6.0", | ||
| "vite": "^8", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "==> apps/desktop/package.json versions"
jq -r '.devDependencies | {vite, "@vitejs/plugin-react", jsdom, typescript, vitest}' apps/desktop/package.json
echo "==> local Vite/Vitest config files"
fd -i 'vite.config.*'
fd -i 'vitest.config.*'
echo "==> references to jsdom environment setup"
rg -n -C2 'jsdom|environment'Repository: agentver/agentver
Length of output: 26970
🏁 Script executed:
# Check vite config for potential compatibility issues
cat -n apps/desktop/vite.config.ts
# Check if apps/desktop/vitest.config.ts references vite config
cat -n apps/desktop/vitest.config.ts
# Check the full current package.json to understand context
cat -n apps/desktop/package.jsonRepository: agentver/agentver
Length of output: 2803
🌐 Web query:
TypeScript 6.0 Vite compatibility requirements
💡 Result:
Vite is fully compatible with TypeScript 6.0. Recent Vite development (as of April 2026) has upgraded its own dev dependencies to TypeScript ~6.0.2 across templates and internal tooling [1][2][3]. Vite 8.0.0 (released March 2026) supports TypeScript config files like vite.config.ts and provides full TypeScript typings for its APIs [4][5]. Vite has no peer dependency on TypeScript and does not perform type-checking itself (relying on tsc or IDE), only transpilation via esbuild or similar [5][6]. Users must ensure tsconfig.json settings like "isolatedModules": true for compatibility with Vite's transpilation model [5]. TypeScript 6.0 changes (e.g., removal of --outFile) align well with Vite as a modern bundler [7][8]. No specific restrictions or additional requirements for TypeScript 6.0 were found in official docs or recent releases [9][10][11].
Citations:
- 1: refactor: upgrade to typescript 6 vitejs/vite#22110
- 2: vitejs/vite@cc41398
- 3: refactor: upgrade to typescript 6 vitejs/vite#22110
- 4: https://main.vitejs.dev/config
- 5: https://vite.dev/guide/features
- 6: https://v4.vitejs.dev/guide/features.html
- 7: https://www.typescriptlang.org/docs/handbook/release-notes/typescript-6-0.html
- 8: https://devblogs.microsoft.com/typescript/announcing-typescript-6-0/
- 9: https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md
- 10: https://vite.dev/releases
- 11: https://www.npmjs.com/package/vite?activeTab=code
🌐 Web query:
@vitejs/plugin-react v6 vite v8 compatibility
💡 Result:
@vitejs/plugin-react v6 is fully compatible with Vite v8. It was specifically released alongside Vite 8 to support its new architecture using Rolldown and Oxc for React Refresh transforms, dropping Babel dependency and Vite 7 support [1][2][3][4]. The official Vite 8 announcement confirms "@vitejs/plugin-react v6" integration [3]. Note that plugin-react v6 requires Vite 8+ and is not compatible with Vite 7 [2][4]. For Babel needs (e.g., React Compiler), pair with @rolldown/plugin-babel [5][3][4]. Older plugin-react v5 works with Vite 8 but lacks v6 optimizations [3].
Citations:
- 1:
plugin-react: addvite@8support vitejs/vite-plugin-react#1012 - 2: Vite 7 compatibility for
@vitejs/plugin-react@6vitejs/vite-plugin-react#1156 - 3: https://vite.dev/blog/announcing-vite8
- 4: https://github.com/vitejs/vite-plugin-react/releases
- 5: After Vite 8, should we turn to @rolldown/plugin-babel for babel plugins? vitejs/vite-plugin-react#1148
Resolve version mismatch between package.json and bun.lock before merge.
The declared major version upgrades (vite ^8, @vitejs/plugin-react ^6, jsdom ^29, typescript ^6.0) are mutually compatible with vitest 4.1.0, and your vite.config.ts and vitest.config.ts configurations are correctly structured. However, bun.lock is severely out of sync: it pins [email protected], @vitejs/plugin-react@^4, and [email protected] whilst package.json declares vite ^8, @vitejs/plugin-react ^6, and jsdom ^29. This will cause install behaviour to differ between lockfile-based and package.json-based installs. Regenerate the lock file to ensure consistency.
🤖 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 `@apps/desktop/package.json` around lines 42 - 46, package.json lists upgraded
majors for vite, `@vitejs/plugin-react`, jsdom and typescript that conflict with
the current bun.lock pins ([email protected], `@vitejs/plugin-react`@^4, [email protected]);
regenerate the lockfile so bun.lock matches package.json by removing or
regenerating bun.lock and running a fresh lockfile install (e.g., bun install)
to produce a new bun.lock that resolves vite ^8, `@vitejs/plugin-react` ^6, jsdom
^29 and typescript ^6.0, then verify vite.config.ts and vitest.config.ts still
work and commit the updated bun.lock together with package.json.
| "@types/react": "^19.0.0", | ||
| "@types/react-dom": "^19.0.0", | ||
| "typescript": "^5.9.3" | ||
| "typescript": "^6.0.3" |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Show website package versions relevant to TS compatibility
jq -r '.name, .dependencies.next, .dependencies.react, .dependencies["react-dom"], .devDependencies.typescript' apps/website/package.json
# Surface TypeScript config inheritance for this app
fd -i 'tsconfig*.json' -x sh -c 'echo "==> $1"; jq -r ".extends, .compilerOptions" "$1" 2>/dev/null || cat "$1"'Repository: agentver/agentver
Length of output: 648
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Find all tsconfig files in the repo
echo "=== Finding tsconfig files ==="
find . -name 'tsconfig*.json' -type f 2>/dev/null | head -20
# Read the website's tsconfig specifically
echo ""
echo "=== Website tsconfig content ==="
if [ -f apps/website/tsconfig.json ]; then
cat apps/website/tsconfig.json
fi
# Check root tsconfig
echo ""
echo "=== Root tsconfig content ==="
if [ -f tsconfig.json ]; then
cat tsconfig.json
fiRepository: agentver/agentver
Length of output: 850
🌐 Web query:
Next.js 16 TypeScript 6.0 compatibility support
💡 Result:
Next.js 16 supports TypeScript 6.0 (as of mid/late 2026). What we can say with evidence: 1) Next.js 16’s published minimum TypeScript requirement is TypeScript 5.1.0+ (not TypeScript 6 specifically). The official Next.js 16 upgrade guide lists “TypeScript 5+” with a minimum of “5.1.0” [1]. 2) The Next.js repo had an explicit change to “Bump TypeScript to 6.0”, merged into the project’s canary flow (a concrete sign that Next.js’ CI/build tooling was updated for TS 6.0) [2]. 3) The Next.js team also backported specific TypeScript v6 deprecations/behavior changes (baseUrl/moduleResolution) into the Next.js 16.2 line, again indicating TS6 compatibility work targeted at the Next.js 16 branch [3]. Practical recommendation (because the official docs only guarantee 5.1.0+ as the minimum): - If you want TS 6.0 specifically, use a recent Next.js 16 release line (or canary) where TS6 support work has landed, and expect any TS 6.0 deprecation-related config changes to be relevant (e.g., baseUrl/moduleResolution deprecations were explicitly handled) [3]. References (most relevant): Next.js 16 minimum TS requirement [1]; merged “Bump TypeScript to 6.0” PR [2]; TS6 deprecations backport for Next.js 16.2 [3].
Citations:
- 1: https://nextjs.org/docs/app/guides/upgrading/version-16
- 2: Bump TypeScript to 6.0 vercel/next.js#91257
- 3: Backport: TypeScript v6 deprecations for baseUrl and moduleResolution vercel/next.js#92130
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Locate the shared TypeScript config package
echo "=== Finding `@agentver/typescript-config` ==="
find . -path '*/typescript-config*' -name 'nextjs.json' -o -path '*/typescript-config*' -type d | head -10
# List the typescript-config package structure
echo ""
echo "=== TypeScript config package content ==="
if [ -d packages/typescript-config ]; then
ls -la packages/typescript-config/
echo ""
if [ -f packages/typescript-config/nextjs.json ]; then
cat packages/typescript-config/nextjs.json
fi
fi
# Check if there are any recent build/type-check issues mentioned in any logs or commits
echo ""
echo "=== Recent git commits touching TypeScript or tsconfig ==="
git log --oneline --all -20 -- '*tsconfig*.json' '*typescript*' 2>/dev/null | head -20 || echo "No recent TypeScript-related commits found"Repository: agentver/agentver
Length of output: 1209
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Read the base TypeScript config
echo "=== TypeScript config base.json ==="
if [ -f packages/typescript-config/base.json ]; then
cat packages/typescript-config/base.json
fiRepository: agentver/agentver
Length of output: 852
Upgrade Next.js to version 16.2 or later to ensure proper TypeScript 6 support.
Next.js 16.1.6 does not include TypeScript 6 compatibility changes. The TypeScript 6 deprecation handling (including fixes for moduleResolution: "NodeNext" used in base.json) was added in Next.js 16.2 and backported to the 16.2+ branch. Current versions create an unsupported toolchain combination. Either upgrade Next.js to ^16.2.0 or downgrade TypeScript to ^5.1.0.
🤖 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 `@apps/website/package.json` at line 24, package.json currently pins
"typescript": "^6.0.3" but the project’s Next.js version is incompatible; update
package.json to either bump Next.js to ^16.2.0 or later (modify the "next"
dependency) to ensure TypeScript 6 support, run a fresh install and test, or
alternatively change the "typescript" entry to "^5.1.0" to match the existing
Next.js version; ensure you update the same package.json that contains the
"typescript" field and run the lockfile update (npm/yarn/pnpm install) and CI to
validate the toolchain.
Bumps the dev-dependencies group with 7 updates in the / directory:
22.19.1925.7.016.4.017.0.45.9.36.0.34.7.06.0.126.1.029.1.16.4.28.0.1216.6.117.4.2Updates
@types/nodefrom 22.19.19 to 25.7.0Commits
Updates
lint-stagedfrom 16.4.0 to 17.0.4Release notes
Sourced from lint-staged's releases.
... (truncated)
Changelog
Sourced from lint-staged's changelog.
... (truncated)
Commits
2862964Merge pull request #1789 from lint-staged/changeset-release/mainc9ecd54chore(changeset): releasecc6b51aMerge pull request #1788 from lint-staged/fix-update-index-againf95c1f8fix: update both default index.lock and non-standard lock when latter existsf44ee68Merge pull request #1786 from lint-staged/update-repo-urla61cf18build(deps): update dependenciesea00037docs: disable Changesets "thanks"ab7c26cdocs: update repo URL to point inlint-staged/lint-stageda36ec1eMerge pull request #1783 from lint-staged/changeset-release/main03ce2a9chore(changeset): releaseUpdates
typescriptfrom 5.9.3 to 6.0.3Release notes
Sourced from typescript's releases.
Commits
050880cBump version to 6.0.3 and LKGeeae9dd🤖 Pick PR #63401 (Also check package name validity in...) into release-6.0 (#...ad1c695🤖 Pick PR #63368 (Harden ATA package name filtering) into release-6.0 (#63372)0725fb4🤖 Pick PR #63310 (Mark class property initializers as...) into release-6.0 (#...607a22aBump version to 6.0.2 and LKG9e72ab7🤖 Pick PR #63239 (Fix missing lib files in reused pro...) into release-6.0 (#...35ff23d🤖 Pick PR #63163 (Port anyFunctionType subtype fix an...) into release-6.0 (#...e175b69Bump version to 6.0.1-rc and LKGaf4caacUpdate LKG8efd7e8Merge remote-tracking branch 'origin/main' into release-6.0Updates
@vitejs/plugin-reactfrom 4.7.0 to 6.0.1Release notes
Sourced from @vitejs/plugin-react's releases.
... (truncated)
Changelog
Sourced from @vitejs/plugin-react's changelog.
... (truncated)
Commits
1e94c06release: [email protected]77c00c0feat(plugin-react): expand@rolldown/plugin-babelpeer dep range (#1146)dcc9012release: [email protected]3a17886docs: add a link to the Oxlint rule for component exports alongside the ESLin...f812135fix(deps): update all non-major dependencies (#1140)a0329a0docs(react): clarify react compiler preset filter (#1137)704e0d3release: [email protected]ac16accfeat(react)!: remove babel (#1123)f01b30cfix(deps): update all non-major dependencies (#1127)b1014bdchore(react): add changelog for #1124Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for
@vitejs/plugin-reactsince your current version.Updates
jsdomfrom 26.1.0 to 29.1.1Release notes
Sourced from jsdom's releases.
... (truncated)
Commits
9b9ea7e29.1.107efb78Optimize computed style comparison5f66329Fix background-origin/background-clip in background shorthandad8af77Fix border shorthand handling5a3e88e29.1.073db204Update dependencies and dev dependenciesa7168a5Support ratio CSS unit type15346e0Fix style cache invalidation2a1e2cd29.0.24097d66Resolve computed CSS values lazily in CSSStyleDeclarationMaintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for jsdom since your current version.
Install script changes
This version modifies
preparescript that runs during installation. Review the package contents before updating.Updates
vitefrom 6.4.2 to 8.0.12Release notes
Sourced from vite's releases.
... (truncated)
Changelog
Sourced from vite's changelog.
... (truncated)
Commits
4dce8b4release: v8.0.12b675c7bfix: refer torolldownOptionsinstead of deprecatedrollupOptionsin mess...66b9eb3chore(deps): update rolldown-related dependencies (#22421)2fe7bd2chore(deps): update dependency eslint-plugin-n to v18 (#22423)2be6000fix(deps): update all non-major dependencies (#22420)d4838a0fix(worker): forward define to worker bundle transform (#22408)cf0ff41feat: update rolldown to 1.0.0 (#22401)3c93fdefix(worker): applybuild.targetto worker bundle (#22404)f5a22e6fix(module-runner): prevent partial-exports race on concurrent imports of in-...66f3194release: v8.0.11Updates
dotenvfrom 16.6.1 to 17.4.2Changelog
Sourced from dotenv's changelog.
... (truncated)
Commits
f116f7017.4.23a81612fix visual order of faq13f55a8Merge branch 'skill'4bbbf73reorganize faqc3da64bMerge pull request #1009 from motdotla/skill6f743b1update sourcefc2c624update skill972315bTighten up skill2795fcereorganize faqd5495d4adjust skillDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsSummary by CodeRabbit
Chores