Repository navigation
chore(deps): update dependency @types/node to v26.6.4 - #3130
renovate[bot] wants to merge 1 commit into
Conversation
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| '@types/node': | ||
| specifier: ^26.1.2 | ||
| version: 26.1.2 | ||
| version: 26.6.4 |
There was a problem hiding this comment.
🟡 Bazel retains old Node types
After @types/node updates to 26.6.4, Bazel still installs 26.1.2. npm_translate_lock reads the unchanged derived lockfile, so Bazel checks do not exercise the updated types.
Learn more
Bazel translates dependencies from the committed derived lockfile via npm_translate_lock, not directly from the lockfile changed here. The derived file still pins @types/node@26.1.2 for the SDK and Cursor extension. Bazel therefore tests a different dependency version from a normal pnpm install.
Example: With this commit checked out, pnpm installs @types/node@26.6.4 for the SDK, while Bazel's @npm repository resolves @types/node@26.1.2.
Recommended fix: Regenerate and commit the derived lockfile using sync-pnpm-lock, then check that its SDK and Cursor importer versions reflect 26.6.4.
Was this helpful? React with 👍 or 👎 to provide feedback.
This PR contains the following updates:
26.1.2→26.6.4Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.