chore(deps): bump dependency updates#594
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
|
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:
📝 WalkthroughWalkthroughBumped the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Suggested labels
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. 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: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@package.json`:
- Line 14: Update package.json to use ts-jest 30+ and ts-node 11+ (replace the
current ts-jest and ts-node versions) to ensure compatibility with "typescript":
"^6.0.2"; then update tsconfig.json to explicitly set any breaking-change
defaults you rely on (add or adjust "strict", "target", "module", and ensure
"rootDir" and "types": ["node"] are present if they were previously inferred) so
the project behavior remains stable under TypeScript 6.0.2.
🪄 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: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 181d196b-6ac2-4594-a8de-d20d8d29e984
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
package.json
vdaas-ci
force-pushed
the
chore/update-npm
branch
from
8ba4d68 to
360ac91
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@package.json`:
- Around line 12-14: The package.json currently pins "typescript": "^6.0.2"
which is incompatible with "ts-jest" ^29.1.4 (peer dependency <6); change the
TypeScript dependency in package.json to a 5.x release compatible with ts-jest
(e.g., "typescript": "^5.2.2" or another 5.x stable you prefer), update the
lockfile (npm/yarn/pnpm install) and run the test suite to confirm; keep
"ts-jest" and "ts-node" unchanged until ts-jest officially supports TS 6.0.
🪄 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: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: d71d3946-63d1-4fd5-80d5-73d40a5ae65a
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
package.json
vdaas-ci
force-pushed
the
chore/update-npm
branch
from
360ac91 to
d937e82
Compare
There was a problem hiding this comment.
♻️ Duplicate comments (1)
package.json (1)
12-14:⚠️ Potential issue | 🔴 CriticalTypeScript 6 bump breaks the Jest TypeScript pipeline with current
ts-jest.
ts-jest(Line 12) is still on^29.1.4, while TS is bumped to^6.0.2(Line 14). In this repo,jest.config.tsusests-jestas the TS transformer, and the installedts-jestpeer range is<6, so this upgrade is currently incompatible.Proposed fix (safe unblock)
- "typescript": "^6.0.2" + "typescript": "^5.4.5"#!/bin/bash # Verify current ts-jest/TypeScript compatibility from authoritative metadata. set -euo pipefail echo "package.json entries:" jq -r '.devDependencies["ts-jest"], .devDependencies["typescript"]' package.json echo echo "Installed lockfile peer constraint for ts-jest:" jq -r '.packages["node_modules/ts-jest"].peerDependencies.typescript' package-lock.json echo echo "Registry peer constraint for ts-jest@29.1.4:" npm view ts-jest@29.1.4 peerDependencies --json | jq -r '.typescript'🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@package.json` around lines 12 - 14, The TypeScript 6 bump is incompatible with the current ts-jest (ts-jest `@29.x`) used as the transformer in jest.config.ts; revert the TypeScript devDependency to a ts-jest-compatible range (e.g. change the typescript entry from "^6.0.2" to a 5.x version such as "^5.2.2" or whatever matches ts-jest's peerDependency) so the installed ts-jest peer constraint is satisfied, then run install and verify tests; alternatively, if you prefer TS 6, upgrade ts-jest to a version that declares support for TypeScript 6 instead of changing typescript.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@package.json`:
- Around line 12-14: The TypeScript 6 bump is incompatible with the current
ts-jest (ts-jest `@29.x`) used as the transformer in jest.config.ts; revert the
TypeScript devDependency to a ts-jest-compatible range (e.g. change the
typescript entry from "^6.0.2" to a 5.x version such as "^5.2.2" or whatever
matches ts-jest's peerDependency) so the installed ts-jest peer constraint is
satisfied, then run install and verify tests; alternatively, if you prefer TS 6,
upgrade ts-jest to a version that declares support for TypeScript 6 instead of
changing typescript.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 5470d865-6a48-496e-9871-1bdd548f5749
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
package.json
vdaas-ci
force-pushed
the
chore/update-npm
branch
from
d937e82 to
e16fb68
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@package.json`:
- Line 14: Change the package.json TypeScript dependency from "typescript":
"^6.0.2" to a compatible 5.x release (for example "typescript": "^5.7.2") so
ts-jest 29.1.4 (which requires "typescript": ">=4.3 <6") will install; then
update your tsconfig.json compilerOptions to explicitly set "moduleResolution":
"node" and add "types": ["jest", "node"] (also ensure sensible options like
"target": "es2020" and "module": "commonjs") so Jest globals are recognized and
module resolution behavior is stable across TS versions.
🪄 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: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 03cb4e33-cf24-4b94-8250-b5fc20fd259e
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
package.json
| "ts-jest": "^29.1.4", | ||
| "ts-node": "^10.9.2", | ||
| "typescript": "^5.4.5" | ||
| "typescript": "^6.0.2" |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check ts-jest peer dependencies for latest versions
echo "=== ts-jest 29.1.4 peer dependencies ==="
npm view ts-jest@29.1.4 peerDependencies
echo -e "\n=== Latest ts-jest version and peer dependencies ==="
npm view ts-jest version peerDependencies
echo -e "\n=== Check for ts-jest versions released in 2026 ==="
npm view ts-jest time --json | jq 'to_entries | map(select(.value | startswith("2026"))) | from_entries'Repository: vdaas/vald-client-node
Length of output: 681
🏁 Script executed:
#!/bin/bash
# Check for ts-jest major versions (especially 30.x)
echo "=== All ts-jest major versions available ==="
npm view ts-jest versions --json | jq -r '.[-20:]' 2>/dev/null || npm view ts-jest versions
echo -e "\n=== ts-jest 30.x peer dependencies (if available) ==="
npm view ts-jest@30 peerDependencies 2>/dev/null || echo "ts-jest@30.x not found"
echo -e "\n=== jest 30.0.2 info ==="
npm view jest@30.0.2 peerDependencies 2>/dev/null || echo "jest@30.0.2 not found"
echo -e "\n=== ts-node 10.9.2 peer dependencies ==="
npm view ts-node@10.9.2 peerDependencies 2>/dev/null || echo "ts-node@10.9.2 info unavailable"
echo -e "\n=== Latest ts-jest that supports TypeScript 6.0 ==="
npm search ts-jest --json 2>/dev/null | jq '.[] | select(.name == "ts-jest") | .version' || echo "Search unavailable"Repository: vdaas/vald-client-node
Length of output: 714
🏁 Script executed:
#!/bin/bash
# Check jest version details more thoroughly
echo "=== jest 30.0.2 existence and info ==="
npm view jest@30.0.2 2>/dev/null || echo "jest@30.0.2 does not exist"
echo -e "\n=== Latest jest version ==="
npm view jest version
echo -e "\n=== jest v30 (major version) info ==="
npm view jest@30 2>/dev/null | head -20 || echo "jest@30 info unavailable"
echo -e "\n=== Check actual package.json jest version ==="
grep -A 2 '"jest"' package.json | head -5Repository: vdaas/vald-client-node
Length of output: 1981
🏁 Script executed:
#!/bin/bash
echo "=== jest 30.0.2 peer dependencies ==="
npm view jest@30.0.2 peerDependencies
echo -e "\n=== `@jest/core` 30.0.2 peer dependencies ==="
npm view "@jest/core@30.0.2" peerDependencies
echo -e "\n=== ts-jest latest versions supporting TypeScript 6.0 (search npm registry) ==="
npm view ts-jest peerDependencies --json | jq '.typescript' 2>/dev/null || echo "Check failed"
echo -e "\n=== Check if any package requires TypeScript explicitly ==="
npm view jest@30.0.2 peerDependencies --json | jq 'keys' 2>/dev/null || echo "No explicit TypeScript peer dep in jest"Repository: vdaas/vald-client-node
Length of output: 425
🏁 Script executed:
#!/bin/bash
echo "=== tsconfig.json content ==="
cat tsconfig.json 2>/dev/null || echo "tsconfig.json not found"
echo -e "\n=== Check for tsconfig files ==="
find . -maxdepth 2 -name "tsconfig*.json" -type f
echo -e "\n=== Check if types field is configured ==="
grep -E '"types"|"moduleResolution"|"rootDir"' tsconfig.json 2>/dev/null || echo "Not found in tsconfig.json"Repository: vdaas/vald-client-node
Length of output: 475
Critical: TypeScript 6.0.2 is incompatible with ts-jest 29.1.4—test suite will fail.
The ts-jest 29.1.4 peer dependency explicitly requires "typescript": ">=4.3 <6", blocking TypeScript 6.0+. npm install will reject this version constraint. No ts-jest version currently supports TypeScript 6.0 (ts-jest 30.x does not exist).
Additionally, your tsconfig.json lacks explicit configuration for TypeScript 6.0 breaking changes:
- Missing
"types": ["jest"]—TypeScript 6.0 disables auto-inclusion by default; Jest globals (describe,it,expect) will be unrecognized. - Missing
"moduleResolution": "node"—TypeScript 6.0 defaults to"bundler", changing module resolution behavior.
Resolution: Downgrade TypeScript to the latest 5.x release (e.g., "typescript": "^5.7.2") and add explicit tsconfig configuration for future TypeScript 6.0 readiness:
tsconfig.json updates
{
"compilerOptions": {
"target": "es2020",
"module": "commonjs",
"moduleResolution": "node",
"types": ["jest", "node"],
"rootDir": "./",
"esModuleInterop": true,
"forceConsistentCasingInFileNames": true,
"strict": true,
"skipLibCheck": true,
"resolveJsonModule": true
}
}🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@package.json` at line 14, Change the package.json TypeScript dependency from
"typescript": "^6.0.2" to a compatible 5.x release (for example "typescript":
"^5.7.2") so ts-jest 29.1.4 (which requires "typescript": ">=4.3 <6") will
install; then update your tsconfig.json compilerOptions to explicitly set
"moduleResolution": "node" and add "types": ["jest", "node"] (also ensure
sensible options like "target": "es2020" and "module": "commonjs") so Jest
globals are recognized and module resolution behavior is stable across TS
versions.
e16fb68 to
c3632aa
Compare
There was a problem hiding this comment.
♻️ Duplicate comments (1)
package.json (1)
14-14:⚠️ Potential issue | 🔴 CriticalCritical: TypeScript 6.0.2 breaks ts-jest 29.1.4 peer dependency constraint—blocking test execution.
The ts-jest 29.1.4 peer dependency explicitly requires TypeScript
>=4.3 <6, preventing installation with TypeScript 6.0.2. Additionally, ts-node 10.9.2 has not declared support for TypeScript 6.x. This dependency mismatch will causenpm installto fail or produce unresolved peer dependency warnings, and the test suite will be non-functional.Resolution: Revert TypeScript to the latest 5.x release (e.g.,
^5.7.2) until ts-jest releases a compatible version supporting TypeScript 6.x.Run the following verification to confirm peer dependency constraints and compatibility:
#!/bin/bash # Verify ts-jest and ts-node compatibility with TypeScript 6.0.2 echo "=== ts-jest 29.1.4 peer dependencies ===" npm view ts-jest@29.1.4 peerDependencies echo -e "\n=== Latest ts-jest version and peer dependencies ===" npm view ts-jest@latest version peerDependencies echo -e "\n=== Check if ts-jest has TypeScript 6 support ===" npm view ts-jest versions --json | jq -r '.[-10:]' echo -e "\n=== ts-node 10.9.2 peer dependencies ===" npm view ts-node@10.9.2 peerDependencies echo -e "\n=== ts-node latest version supporting TypeScript 6 ===" npm view ts-node@latest version peerDependencies echo -e "\n=== Verify jest 30.0.2 existence ===" npm view jest@30.0.2 version || echo "jest@30.0.2 does not exist" echo -e "\n=== Latest TypeScript 5.x version ===" npm view typescript@5 version🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@package.json` at line 14, The package.json currently pins "typescript": "^6.0.2", which conflicts with ts-jest@29.1.4 and ts-node 10.9.2 peer constraints; change the TypeScript devDependency back to the latest 5.x (e.g., update the "typescript" entry to "^5.7.2") so npm install and the test suite can run, and then run npm install and the reviewer-provided verification script to confirm ts-jest/ts-node compatibility; ensure you update only the "typescript" entry in package.json and do not alter ts-jest or ts-node versions.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@package.json`:
- Line 14: The package.json currently pins "typescript": "^6.0.2", which
conflicts with ts-jest@29.1.4 and ts-node 10.9.2 peer constraints; change the
TypeScript devDependency back to the latest 5.x (e.g., update the "typescript"
entry to "^5.7.2") so npm install and the test suite can run, and then run npm
install and the reviewer-provided verification script to confirm ts-jest/ts-node
compatibility; ensure you update only the "typescript" entry in package.json and
do not alter ts-jest or ts-node versions.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: dc7f483e-87e5-42a1-a0f6-4057d0fec01f
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
package.json
vdaas-ci
force-pushed
the
chore/update-npm
branch
7 times, most recently
from
4de32dc to
111ac38
Compare
vdaas-ci
force-pushed
the
chore/update-npm
branch
6 times, most recently
from
711a3b3 to
10aacce
Compare
vdaas-ci
force-pushed
the
chore/update-npm
branch
6 times, most recently
from
1f272e1 to
91fb5fc
Compare
vdaas-ci
force-pushed
the
chore/update-npm
branch
6 times, most recently
from
3ba3cd0 to
c135a5f
Compare
vdaas-ci
force-pushed
the
chore/update-npm
branch
6 times, most recently
from
00e2afc to
5f5be37
Compare
vdaas-ci
force-pushed
the
chore/update-npm
branch
5 times, most recently
from
2d5d765 to
5a44c5b
Compare
Signed-off-by: vdaas-ci <vald@vdaas.org>
vdaas-ci
force-pushed
the
chore/update-npm
branch
from
5a44c5b to
8888283
Compare
2 participants
Automated pull request to update dependencies.