build(deps-dev): bump the npm-minor-patch group across 1 directory with 3 updates

[dependabot]

Bumps the npm-minor-patch group with 3 updates in the /editors/vscode directory: @types/vscode, @vscode/vsce and esbuild.

Updates @types/vscode from 1.120.0 to 1.125.0

Commits

• See full diff in compare view

Updates @vscode/vsce from 3.9.1 to 3.9.2

Release notes

Sourced from @​vscode/vsce's releases.

v3.9.2

Changes:

• #1283: fix: skip APIScan
• #1282: chore: bump CI to Node 22 and fix build
• #1279: Bump the uuid test fixture version to 100.0.0
• #1278: Bump tmp from 0.2.4 to 0.2.6
• #1277: Bump qs from 6.14.2 to 6.15.2
• #1276: Bump uuid and @​azure/msal-node
• #1274: Run npm audit fix
• #1272: Bump fast-uri from 3.0.6 to 3.1.2
• #1267: Bump minimatch from 10.2.2 to 10.2.3
• #1247: Update minimatch dependency to v10

This list of changes was auto generated.

v3.9.2-4

Changes:

• #1283: fix: skip APIScan
• #1282: chore: bump CI to Node 22 and fix build
• #1279: Bump the uuid test fixture version to 100.0.0
• #1278: Bump tmp from 0.2.4 to 0.2.6
• #1277: Bump qs from 6.14.2 to 6.15.2
• #1276: Bump uuid and @​azure/msal-node

This list of changes was auto generated.

v3.9.2-3

Changes:

• #1274: Run npm audit fix

This list of changes was auto generated.

v3.9.2-2

Changes:

• #1272: Bump fast-uri from 3.0.6 to 3.1.2

This list of changes was auto generated.

... (truncated)

Commits

• f7501f2 fix: skip APIScan (#1283)
• 7cd3244 chore: bump CI to Node 22 and fix build (#1282)
• df1a68e Bump the uuid test fixture version to 100.0.0 (#1279)
• 3a5786e Merge pull request #1278 from microsoft/dependabot/npm_and_yarn/tmp-0.2.6
• 4954e08 Bump tmp from 0.2.4 to 0.2.6
• 54dce87 Bump qs from 6.14.2 to 6.15.2 (#1277)
• 86fc2d6 Bump uuid and @​azure/msal-node (#1276)
• 4699582 Run npm audit fix and update lockfile (#1274)
• e003a0a Merge pull request #1272 from microsoft/dependabot/npm_and_yarn/fast-uri-3.1.2
• 74ab7a9 Bump fast-uri from 3.0.6 to 3.1.2
• Additional commits viewable in compare view

Updates esbuild from 0.28.0 to 0.28.1

Release notes

Sourced from esbuild's releases.

v0.28.1

• Disallow \ in local development server HTTP requests (GHSA-g7r4-m6w7-qqqr)

  This release fixes a security issue where HTTP requests to esbuild's local development server could traverse outside of the serve directory on Windows using a \ backslash character. It happened due to the use of Go's path.Clean() function, which only handles Unix-style / characters. HTTP requests with paths containing \ are no longer allowed.

  Thanks to @​dellalibera for reporting this issue.

• Add integrity checks to the Deno API (GHSA-gv7w-rqvm-qjhr)

  The previous release of esbuild added integrity checks to esbuild's npm install script. This release also adds integrity checks to esbuild's Deno install script. Now esbuild's Deno API will also fail with an error if the downloaded esbuild binary contains something other than the expected content.

  Note that esbuild's Deno API installs from registry.npmjs.org by default, but allows the NPM_CONFIG_REGISTRY environment variable to override this with a custom package registry. This change means that the esbuild executable served by NPM_CONFIG_REGISTRY must now match the expected content.

  Thanks to @​sondt99 for reporting this issue.

• Avoid inlining using and await using declarations (#4482)

  Previously esbuild's minifier sometimes incorrectly inlined using and await using declarations into subsequent uses of that declaration, which then fails to dispose of the resource correctly. This bug happened because inlining was done for let and const declarations by avoiding doing it for var declarations, which no longer worked when more declaration types were added. Here's an example:

  // Original code
  {
    using x = new Resource()
    x.activate()
  }
  // Old output (with --minify)
  new Resource().activate();
  // New output (with --minify)
  {using e=new Resource;e.activate()}

• Fix module evaluation when an error is thrown (#4461, #4467)

  If an error is thrown during module evaluation, esbuild previously didn't preserve the state of the module for subsequent module references. This was observable if import() or require() is used to import a module multiple times. The thrown error is supposed to be thrown by every call to import() or require(), not just the first. With this release, esbuild will now throw the same error every time you call import() or require() on a module that throws during its evaluation.

• Fix some edge cases around the new operator (#4477)

  Previously esbuild incorrectly printed certain edge cases involving complex expressions inside the target of a new expression (specifically an optional chain and/or a tagged template literal). The generated code for the new target was not correctly wrapped with parentheses, and either contained a syntax error or had different semantics. These edge cases have been fixed so that they now correctly wrap the new target in parentheses. Here is an example of some affected code:

  // Original code
  new (foo()`bar`)()
  new (foo()?.bar)()
  // Old output
  new foo()bar();
  new (foo())?.bar();

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.28.1

• Disallow \ in local development server HTTP requests (GHSA-g7r4-m6w7-qqqr)

  This release fixes a security issue where HTTP requests to esbuild's local development server could traverse outside of the serve directory on Windows using a \ backslash character. It happened due to the use of Go's path.Clean() function, which only handles Unix-style / characters. HTTP requests with paths containing \ are no longer allowed.

  Thanks to @​dellalibera for reporting this issue.

• Add integrity checks to the Deno API (GHSA-gv7w-rqvm-qjhr)

  The previous release of esbuild added integrity checks to esbuild's npm install script. This release also adds integrity checks to esbuild's Deno install script. Now esbuild's Deno API will also fail with an error if the downloaded esbuild binary contains something other than the expected content.

  Note that esbuild's Deno API installs from registry.npmjs.org by default, but allows the NPM_CONFIG_REGISTRY environment variable to override this with a custom package registry. This change means that the esbuild executable served by NPM_CONFIG_REGISTRY must now match the expected content.

  Thanks to @​sondt99 for reporting this issue.

• Avoid inlining using and await using declarations (#4482)

  Previously esbuild's minifier sometimes incorrectly inlined using and await using declarations into subsequent uses of that declaration, which then fails to dispose of the resource correctly. This bug happened because inlining was done for let and const declarations by avoiding doing it for var declarations, which no longer worked when more declaration types were added. Here's an example:

  // Original code
  {
    using x = new Resource()
    x.activate()
  }
  // Old output (with --minify)
  new Resource().activate();
  // New output (with --minify)
  {using e=new Resource;e.activate()}

• Fix module evaluation when an error is thrown (#4461, #4467)

  If an error is thrown during module evaluation, esbuild previously didn't preserve the state of the module for subsequent module references. This was observable if import() or require() is used to import a module multiple times. The thrown error is supposed to be thrown by every call to import() or require(), not just the first. With this release, esbuild will now throw the same error every time you call import() or require() on a module that throws during its evaluation.

• Fix some edge cases around the new operator (#4477)

  Previously esbuild incorrectly printed certain edge cases involving complex expressions inside the target of a new expression (specifically an optional chain and/or a tagged template literal). The generated code for the new target was not correctly wrapped with parentheses, and either contained a syntax error or had different semantics. These edge cases have been fixed so that they now correctly wrap the new target in parentheses. Here is an example of some affected code:

  // Original code
  new (foo()`bar`)()
  new (foo()?.bar)()
  // Old output
  new foo()bar();
  new (foo())?.bar();

... (truncated)

Commits

• bb9db84 publish 0.28.1 to npm
• 9ff053e security: add integrity checks to the Deno API
• 0a9bf21 enforce non-negative size in gzip parser
• e2a1a71 security: forbid \\ in local dev server requests
• 83a2cbf fix #4482: don't inline using declarations
• 308ad74 fix #4471: renaming of nested var declarations
• f013f5f fix some typos
• aafd6e4 chore: fix some minor issues in comments (#4462)
• 15300c3 follow up: cjs evaluation fixes
• 1bda0c3 fix #4461, fix #4467: esm evaluation fixes
• Additional commits viewable in compare view

[dependabot]

Labels

The following labels could not be found: dependencies, vscode. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[kaeawc]

@dependabot rebase

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.