Skip to content

chore(deps-dev): bump @types/node and eslint in /vscode-bino - #83

Open
ThatScalaGuy wants to merge 1 commit into
mainfrom
chore/deps-vscode-node-eslint
Open

chore(deps-dev): bump @types/node and eslint in /vscode-bino#83
ThatScalaGuy wants to merge 1 commit into
mainfrom
chore/deps-vscode-node-eslint

Conversation

@ThatScalaGuy

Copy link
Copy Markdown
Contributor

Carries the safe subset of the npm-minor-patch group from dependabot #76:

  • @types/node 25.9.1 → 25.9.3
  • eslint 10.4.1 → 10.5.0

esbuild 0.28.1 already landed via #75.

Why this instead of #76

#76 also bumped @types/vscode 1.85.0 → 1.120.0. That fails vsce package at release time:

ERROR  @types/vscode 1.120.0 greater than engines.vscode ^1.85.0. Either upgrade engines.vscode or use an older @types/vscode version

The CI VS Code Extension job only runs npm run compile, so it doesn't catch this — but release.yml's build-vscode-extension job runs vsce package, which the release needs. Rather than raise engines.vscode (which would lift the minimum supported VS Code version by ~35 releases), this keeps @types/vscode pinned at the engines floor and adds a dependabot ignore for it so the broken bump isn't re-proposed until we intentionally raise the minimum.

dependabot auto-closed #76 after #75 merged, so this lands the remaining safe updates on a clean branch.

Verified locally: npm ci, npm run compile, and vsce package all succeed.

Carries the safe subset of the npm-minor-patch group (dependabot #76):
@types/node 25.9.1 -> 25.9.3 and eslint 10.4.1 -> 10.5.0. esbuild 0.28.1
already landed via #75.

Drops the group's @types/vscode 1.85.0 -> 1.120.0 bump: 1.120.0 exceeds
engines.vscode (^1.85.0), which makes `vsce package` fail at release time
(the CI compile step does not catch this). Add a dependabot ignore for
@types/vscode so it is not re-proposed until the minimum supported VS Code
version is intentionally raised.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant