-
Notifications
You must be signed in to change notification settings - Fork 10
chore(deps): update all dependencies #318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -38,7 +38,7 @@ | |
| "packageManager": "bun@1.3.11", | ||
| "devDependencies": { | ||
| "@effect/vitest": "^0.29.0", | ||
| "@types/node": "^25.8.0", | ||
| "@types/node": "^25.9.0", | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🧩 Analysis chain🏁 Script executed: #!/bin/bash
# Verify typecheck passes with updated `@types/node`
cd packages/docker-git-session-sync
bun run typecheckRepository: ProverCoderAI/docker-git Length of output: 112 🏁 Script executed: #!/bin/bash
# Check Node.js version target and existing dependencies
cd packages/docker-git-session-sync
echo "=== package.json content ==="
cat package.json | head -50
echo -e "\n=== Root package.json for Node version info ==="
cat ../../package.json | grep -A 5 -B 5 "engines\|node"
echo -e "\n=== Check for tsconfig.json ==="
find . -name "tsconfig.json" -o -name "tsconfig*.json" | xargs cat 2>/dev/null || echo "No tsconfig found in this package"Repository: ProverCoderAI/docker-git Length of output: 3023 🏁 Script executed: #!/bin/bash
# Search for `@types/node` and TypeScript version info in repository
echo "=== Looking for TypeScript version ==="
rg "`@types/node`|typescript" package.json --max-count=5 -A 1 | head -30
echo -e "\n=== Check root package.json ==="
cat package.json | grep -E "typescript|`@types/node`" -A 1 -B 1
echo -e "\n=== Node.js engine requirements ==="
cat package.json | grep -E "engines|\"node\""Repository: ProverCoderAI/docker-git Length of output: 177 🏁 Script executed: #!/bin/bash
# Check root tsconfig.base.json and Node.js version requirement
echo "=== Root tsconfig.base.json ==="
cat tsconfig.base.json | head -30
echo -e "\n=== Root package.json - engines/node requirement ==="
cat package.json | grep -A 10 "\"engines\""Repository: ProverCoderAI/docker-git Length of output: 939 🌐 Web query:
💡 Result: The Citations:
🏁 Script executed: #!/bin/bash
# Check for Node.js version specifications
echo "=== Looking for .nvmrc or .node-version ==="
find . -name ".nvmrc" -o -name ".node-version" | xargs cat 2>/dev/null || echo "Not found"
echo -e "\n=== Check CI/CD workflows ==="
find . -path "*/.*github/workflows" -o -path "*/.gitlab-ci.yml" | head -10
echo -e "\n=== Look for Dockerfile Node base image ==="
find . -name "Dockerfile*" | xargs grep -i "FROM.*node" 2>/dev/null | head -5
echo -e "\n=== Check package.json packageManager and Node version ==="
cat package.json | grep -E "packageManager|engines|node" || echo "No explicit engine requirement"
echo -e "\n=== Check if there are other `@types/node` versions in workspace ==="
find packages -name "package.json" | xargs grep "`@types/node`" | head -20Repository: ProverCoderAI/docker-git Length of output: 794 🏁 Script executed: #!/bin/bash
# Search for actual Node.js usage and version clues
echo "=== Check for minimum Node.js version in code comments ==="
rg "node.*20|node.*22|node.*24|Node.js.*2[0-9]" --max-count=10
echo -e "\n=== Check if this is a type definitions only package ==="
cat packages/docker-git-session-sync/package.json | grep -E "\"main\"|\"types\"|\"exports\"" -A 1Repository: ProverCoderAI/docker-git Length of output: 4078 Версия Проект использует Используйте:
Текущая версия вызовет несоответствия типов и проблемы при типизации. 🤖 Prompt for AI Agents |
||
| "@vitejs/plugin-react": "^6.0.2", | ||
| "typescript": "^6.0.3", | ||
| "vite": "^8.0.13", | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
Does@types/nodeversion 25.9.0 exist on npm and are there any known security issues?💡 Result:
The npm package
@types/nodedoes not have a version 25.9.0 [1][2]. While Node.js itself has a version 25.9.0 [3][4], the@types/nodepackage follows a different versioning scheme where the major and minor versions align with Node.js, but the patch version is managed independently by the DefinitelyTyped project [5]. As of May 18, 2026, the latest available version of@types/nodeis 25.7.0 [2]. Regarding security, there are no direct vulnerabilities reported for the@types/nodepackage in the Snyk vulnerability database [2]. It is important to note that@types/nodeis a development dependency containing only TypeScript type definitions and does not contain executable code, which significantly reduces its security risk profile. Users should be aware of a separate, malicious package named types-node (note the missing @ symbol), which has been identified as malicious and should be avoided [6]. Additionally, while there have been recent, unrelated supply chain attacks targeting other popular Node.js packages like node-ipc [7][8][9], these do not affect@types/node.Citations:
🌐 Web query:
Does@typescript-eslint/eslint-pluginversion 8.59.4 exist on npm and are there any known security issues?💡 Result:
As of May 18, 2026, version 8.59.4 of
@typescript-eslint/eslint-plugindoes not exist on npm [1][2]. The latest stable releases for the 8.x branch have reached 8.59.3 [1]. There are no known direct security vulnerabilities associated with the current versions of@typescript-eslint/eslint-plugin[3]. While security tools like Snyk and other vulnerability databases monitor the package, it is consistently reported as having no known direct security issues [3][4]. Users are generally advised to keep the package updated to the latest stable version to ensure they have the most recent security patches for any transitive dependencies [5]. If you encounter security warnings in your project, they often stem from transitive dependencies (such as minimatch) rather than the plugin itself, and these are typically resolved by updating to the latest version of@typescript-eslint/eslint-plugin[5].Citations:
🏁 Script executed:
Repository: ProverCoderAI/docker-git
Length of output: 112
Указанные версии пакетов не существуют на npm.
Версия
@types/node@25.9.0не опубликована на npm. На май 2026 г. последняя доступная версия —25.7.0. Версия@typescript-eslint/eslint-plugin@8.59.4также не существует; в ветке 8.x последняя стабильная версия —8.59.3.Обновите package.json, используя существующие версии:
@types/node@^25.7.0(или актуальнейшую доступную)@typescript-eslint/eslint-plugin@^8.59.3(или актуальнейшую доступную)@typescript-eslint/parser@^8.59.3(синхронизируйте версию с eslint-plugin)После исправления разрешений версий выполните
bun run typecheckиbun run checkдля проверки совместимости обновленных зависимостей с кодовой базой.🤖 Prompt for AI Agents