Repository navigation
chore(deps): Clear the security alerts of the n8n node lockfile - #52
Merged
Merged
Conversation
- npm audit fix: follow-redirects 1.16.3, undici 7.30.2 and eslint-plugin-import-x 4.18.1. - @n8n/node-cli 0.51.4 to 0.57.4 (dev). It pins handlebars 4.7.10 and axios 1.20.0. - vitest 3 to 4.1.12 (dev). It brings @vitest/mocker 4.1.12 and drops tinypool. The compiled node and credential files in dist are the same. The package version does not change.
There was a problem hiding this comment.
🟡 Changes recommended
The package’s declared Node.js minimum is incompatible with the upgraded Vitest/Vite toolchain, leaving an active installation and build failure risk for supported environments.
1 open issue
1 file not reviewed
packages/n8n-nodes-taskade/package-lock.json: Generated file
What changed in this PR
Updates the Taskade n8n node’s development toolchain and lockfile to address reachable security alerts without changing the published package version or runtime dependency surface.
Changes:
- Upgrades
@n8n/node-clifrom0.51.4to0.57.4. - Upgrades Vitest from
^3.2.4to^4.1.12. - Refreshes transitive dependencies, including patched
follow-redirects,undici,handlebars, andaxiosversions. - The updated Vitest toolchain resolves Vite/Rolldown versions requiring Node
>=20.19, while the package still declares Node>=20.15.
| File | Description |
|---|---|
| packages/n8n-nodes-taskade/package.json | Updates the development CLI and Vitest dependencies. |
| packages/n8n-nodes-taskade/package-lock.json | Records the updated dependency graph and refreshed security-related transitive dependencies. |
Review effort: Lite
| "n8n-workflow": "2.49.1", | ||
| "typescript": "5.9.3", | ||
| "vitest": "^3.2.4" | ||
| "vitest": "^4.1.12" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Clears the Dependabot alerts on
packages/n8n-nodes-taskade/package-lock.jsonthat a fix can reach. The package manager stays npm. Only dev dependencies change. The packageversionstays 1.0.1, and this PR adds no tag.What changes
npm audit fixfollow-redirects,undici@n8n/node-cli0.51.4 to 0.57.4 (dev, exact pin kept)handlebars(4.7.10),axios(1.20.0)vitest^3.2.4 to ^4.1.12 (dev)vitest,@vitest/mocker(4.1.12),tinypool(vitest 4 does not use it)The alerts for
form-dataandlodashpoint at versions that #42 already replaced. They close when Dependabot scansmasteragain.Checks
npm ci --ignore-scripts,npm run lint,npm test(2 files, 51 tests) andnpm run buildpass locally.distbefore and after shows one changed file, the copy ofpackage.json, in itsdevDependencies. Every compiled node, credential and icon file is the same.Alerts that stay open
The newest
@n8n/node-cli(0.57.4) pins these packages through@n8n/ai-node-sdkand@oclif/core. No release of the CLI fixes them yet:qs6.16.0:@n8n/backend-network1.22.4 pins it exactly.stream-json1.9.1:@n8n/backend-common1.48.4 pins it exactly. The fix is in 3.x.uuid10.0.0:@langchain/classic1.0.27 asks for^10.0.0. The fix is in 11.x.minimatch10.2.6:@oclif/core4 asks for^10.2.5. The fix is in 11.x.All of them are dev-only. They do not reach the published package, which ships only
dist.