chore(deps): rolling dependency update - #81
Open
socket-pr-bot[bot] wants to merge 1 commit into
Open
socket-pr-bot[bot] wants to merge 1 commit into
socket-pr-bot[bot] wants to merge 1 commit into
Conversation
socket-pr-bot
Bot
force-pushed
the
weekly-update
branch
from
September 19, 2026 08:20
9caa7dc to
f612165
Compare
socket-pr-bot
Bot
force-pushed
the
weekly-update
branch
from
September 20, 2026 08:20
f612165 to
751f18d
Compare
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.
Rolling dependency update
One long-lived PR, rebuilt from
mainon every run so it staysmergeable. Each run appends its dependency delta below, newest first.
2026-09-20 — run · no dependency changes
No dependency ranges changed in this run.
commits
2026-09-19 — run · no dependency changes
No dependency ranges changed in this run.
commits
2026-09-18 — run · no dependency changes
No dependency ranges changed in this run.
commits
Note
Low Risk
Toolchain and lockfile pin updates only; no extension runtime or security-sensitive application logic changes.
Overview
Bumps the pinned Node version from 26.8.1 to 26.8.2 in
.node-version.package.jsondevEngines.packageManageris no longer a single pnpm entry; it is now an array that enforces both npm (^11.19.0 || >=12.0.2) and pnpm (^11.25.0 || >=12.3.4), each withonFail: "error". The existingengines.npm/engines.pnpmranges are unchanged.pnpm-lock.yamlupdates the bundled pnpm toolchain from 12.4.2 to 12.4.1 (including all@pnpm/exe.*platform packages).Reviewed by Cursor Bugbot for commit 9caa7dc. Configure here.