Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -78,15 +78,15 @@
"@google-cloud/nodejs-repo-tools": "^3.0.0",
"async": "^2.6.0",
"codecov": "^3.0.0",
"eslint": "^4.11.0",
"eslint": "^9.0.0",
"eslint-config-prettier": "^2.8.0",
"eslint-plugin-node": "^6.0.0",
"eslint-plugin-prettier": "^2.3.1",
"ink-docstrap": "^1.3.2",
"intelli-espower-loader": "^1.0.1",
"jsdoc": "^3.5.5",
"mocha": "^5.0.0",
"nyc": "^11.3.0",
"jsdoc": "^4.0.3",
"mocha": "^11.0.1",
"nyc": "^15.0.0",
Comment on lines +81 to +89
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

These dependency upgrades introduce breaking changes due to their Node.js version requirements, which are incompatible with this project's supported Node version (>=4.0.0 as defined in engines).

Specifically:

  • eslint@9.0.0 requires Node.js ^18.18.0 || ^20.9.0 || >=22.0.0.
  • mocha@11.0.1 requires Node.js ^18.18.0 || ^20.9.0 || >=22.0.0.
  • jsdoc@4.0.3 requires Node.js >=16.0.0.
  • nyc@15.0.0 requires Node.js >=8.

Merging these changes will cause failures in development and CI environments running on older Node.js versions. To proceed, you'll either need to update the project's supported Node.js version in package.json or find alternative package versions that fix the vulnerabilities while remaining compatible with your supported Node.js range.

"power-assert": "^1.4.4",
"prettier": "^1.9.1",
"proxyquire": "^1.7.10"
Expand Down
Loading