Skip to content

Bump the development-dependencies group across 1 directory with 8 updates #1912

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

Bump the development-dependencies group across 1 directory with 8 updates #1912

wants to merge 1 commit into from

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 9, 2024 •
edited
Loading

Bumps the development-dependencies group with 8 updates in the / directory:

Package From To
@types/node 20.17.0 22.10.1
@vscode/test-cli 0.0.9 0.0.10
@vscode/test-web 0.0.56 0.0.65
chai 4.5.0 5.1.2
@types/chai 4.3.10 5.0.1
esbuild 0.23.1 0.24.0
mocha 10.8.2 11.0.1
msw 2.2.13 2.6.8

Updates @types/node from 20.17.0 to 22.10.1

Commits

Updates @vscode/test-cli from 0.0.9 to 0.0.10

Changelog

Sourced from @​vscode/test-cli's changelog.

Changelog

TBA

  • Fix bailing multiple configs on first failure (fixes #44)
  • Fix extension install on Windows on modern Node versions (fixes #43)
  • Normalize casing in paths (fixes #49)
Commits

Updates @vscode/test-web from 0.0.56 to 0.0.65

Release notes

Sourced from @​vscode/test-web's releases.

v0.0.65

Changes:

  • #151: Set publishRequiresApproval to false in pipeline configuration
  • #150: prepare 0.0.65

This list of changes was auto generated.

v0.0.64

Changes:

  • #149: prepare 0.0.64
  • #148: VS Code main has moved back to npm, we could catch it
  • #147: apply learnings from wsl download fix

This list of changes was auto generated.

v0.0.63

Changes:

  • #146: prepare 0.0.63
  • #142: Bump path-to-regexp from 6.2.2 to 6.3.0

This list of changes was auto generated.

v0.0.62

Changes:

  • #144: detect ESM from root package.json

This list of changes was auto generated.

v0.0.61

Changes:

  • #143: prepare 0.61.0

This list of changes was auto generated.

v0.0.60

... (truncated)

Changelog

Sourced from @​vscode/test-web's changelog.

Changelog

0.0.58

  • new option --commit to specify the build of VS Code to use. By default the latest build is used.

0.0.37

  • new option --testRunnerDataDir to set the temporary folder for storing the VS Code builds used for running the tests

0.0.28

  • new option --coi to enable cross origin isolation.

0.0.22

  • new option --printServerLog replacing --hideServerLog.
  • new option --browser replacing --browserType.

0.0.20

  • new option --extensionId publisher.name[@prerelease] to include one or more extensions.

0.0.18

  • new option --browserType none to start the server without opening a browser.

0.0.17

  • new options --host and --port: If provided runs the server from the given host and port.
  • new option --verbose to print out the browser console log.

0.0.16

  • new option --sourcesPath: If provided, runs the server from VS Code sources at the given location.
  • option --version is deprecated and replaced with quality. Supported values: stable, insiders. Instead of sources use --insiders.

0.0.14

  • new option --extensionPath : A path pointing to a folder containing additional extensions to include. Argument can be provided multiple times.
  • new option --permission: Permission granted to the opened browser: e.g. clipboard-read, clipboard-write. See full list of options here. Argument can be provided multiple times.
  • new option --hideServerLog: If set, hides the server log. Defaults to true when an extensionTestsPath is provided, otherwise false.
  • close server when browser is closed

0.0.9

  • new option folderPath: A local folder to open VS Code on. The folder content will be available as a virtual file system and opened as workspace.

0.0.1 |

  • Initial version
Commits
Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for @​vscode/test-web since your current version.


Updates chai from 4.5.0 to 5.1.2

Release notes

Sourced from chai's releases.

v5.1.2

What's Changed

Full Changelog: chaijs/chai@v5.1.1...v5.1.2

v5.1.1

What's Changed

New Contributors

Full Changelog: chaijs/chai@v5.1.0...v5.1.1

v5.1.0

What's Changed

New Contributors

Full Changelog: chaijs/chai@v5.0.3...v5.1.0

v5.0.3

Fix bad v5.0.2 publish.

Full Changelog: chaijs/chai@v5.0.2...v5.0.3

v5.0.2

What's Changed

... (truncated)

Commits

Updates @types/chai from 4.3.10 to 5.0.1

Commits

Updates esbuild from 0.23.1 to 0.24.0

Release notes

Sourced from esbuild's releases.

v0.24.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.23.0 or ~0.23.0. See npm's documentation about semver for more information.

  • Drop support for older platforms (#3902)

    This release drops support for the following operating system:

    • macOS 10.15 Catalina

    This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

    Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

    git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild --version

  • Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

    Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

  • Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

    TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

  • Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

    Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

  • Work around more issues with Deno 1.31+ (#3917)

    This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

    This fix was contributed by @​Joshix-1.

Changelog

Sourced from esbuild's changelog.

0.24.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.23.0 or ~0.23.0. See npm's documentation about semver for more information.

  • Drop support for older platforms (#3902)

    This release drops support for the following operating system:

    • macOS 10.15 Catalina

    This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

    Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

    git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild --version

  • Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

    Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

  • Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

    TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

  • Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

    Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

  • Work around more issues with Deno 1.31+ (#3917)

    This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

    This fix was contributed by @​Joshix-1.

Commits

Updates mocha from 10.8.2 to 11.0.1

Release notes

Sourced from mocha's releases.

v11.0.1

11.0.1 (2024-12-02)

🌟 Features

📚 Documentation

  • fix examples for linkPartialObjects methods (#5255) (34e0e52)

v11.0.0 Prerelease

11.0.0 (2024-11-11)

⚠ BREAKING CHANGES

  • adapt new engine range for Mocha 11 (#5216)

🌟 Features

🩹 Fixes

📚 Documentation

Changelog

Sourced from mocha's changelog.

11.0.1 (2024-12-02)

🌟 Features

📚 Documentation

  • fix examples for linkPartialObjects methods (#5255) (34e0e52)

11.0.0 (2024-11-11)

⚠ BREAKING CHANGES

  • adapt new engine range for Mocha 11 (#5216)

🌟 Features

🩹 Fixes

📚 Documentation

Commits

Updates msw from 2.2.13 to 2.6.8

Release notes

Sourced from msw's releases.

v2.6.8 (2024-12-07)

Bug Fixes

  • setupServer: reapply interception after calling server.listen() after server.close() (#2383) (00da9cad4249b61732ee375d9dbefeb76028cc2b) @​kettanaito

v2.6.7 (2024-12-06)

Bug Fixes

v2.6.6 (2024-11-22)

Bug Fixes

  • types: support optional path parameters (#2368) (3b7b776e8c0de341185df4686a895c24326748d3) @​kettanaito

v2.6.5 (2024-11-16)

Bug Fixes

  • support non-configurable responses (#2360) (5bf3e3bf5f9a6d32c79410c11abd539ec4c2ddc5) @​kettanaito

v2.6.4 (2024-11-10)

Bug Fixes

  • prevent infinite loop when bypassing sendBeacon() requests (#2353) (2fa98c327acc51189f87789d9155c4ec57be2299) @​kettanaito
  • remove the internal bypass request header before performing the request as-is in Node.js (#2353) (2fa98c327acc51189f87789d9155c4ec57be2299) @​kettanaito

v2.6.3 (2024-11-10)

Bug Fixes

  • handleRequest: remove transformResponse option (#2351) (74c4a3a89970bbfc498c812790daef13766dea72) @​kettanaito

v2.6.2 (2024-11-07)

Bug Fixes

  • update @bundled-es-modules/cookie to 2.0.1 (#2312) (c134352e8206b91740247f4f196767ab8a8eb921) @​kettanaito

v2.6.1 (2024-11-06)

Bug Fixes

  • prevent instanceof handler check failures between different MSW versions (#2349) (28d26bd7fa585d76f9ca69a67dfa70a234450ed9) @​kettanaito

v2.6.0 (2024-10-29)

... (truncated)

Commits
  • de3bedf chore(release): v2.6.8
  • 00da9ca fix(setupServer): reapply interception after calling server.listen() after ...
  • e8d748e chore(ci): fix broken restore cache key
  • 6a2cf33 chore(release): v2.6.7
  • 3f40055 fix(setupWorker): correctly delete internal accept header on passthrough (#...
  • e61ee12 chore: use pnpm@9.14.0 for preview releases
  • c86ad58 ci: run ci build related tests in parallel (#1907)
  • bd5f47c chore: update to vitest@2 (#2379)
  • 48e4c76 chore: update pnpm to v9.14.0 (#2211)
  • 3cc9d9f chore(release): v2.6.6
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
Bump the development-dependencies group across 1 directory with 8 upd…
c2c9599 
…ates

Bumps the development-dependencies group with 8 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `20.17.0` | `22.10.1` |
| [@vscode/test-cli](https://github.com/Microsoft/vscode-test-cli) | `0.0.9` | `0.0.10` |
| [@vscode/test-web](https://github.com/microsoft/vscode-test-web) | `0.0.56` | `0.0.65` |
| [chai](https://github.com/chaijs/chai) | `4.5.0` | `5.1.2` |
| [@types/chai](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/chai) | `4.3.10` | `5.0.1` |
| [esbuild](https://github.com/evanw/esbuild) | `0.23.1` | `0.24.0` |
| [mocha](https://github.com/mochajs/mocha) | `10.8.2` | `11.0.1` |
| [msw](https://github.com/mswjs/msw) | `2.2.13` | `2.6.8` |



Updates `@types/node` from 20.17.0 to 22.10.1
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

Updates `@vscode/test-cli` from 0.0.9 to 0.0.10
- [Changelog](https://github.com/microsoft/vscode-test-cli/blob/main/CHANGELOG.md)
- [Commits](https://github.com/Microsoft/vscode-test-cli/commits)

Updates `@vscode/test-web` from 0.0.56 to 0.0.65
- [Release notes](https://github.com/microsoft/vscode-test-web/releases)
- [Changelog](https://github.com/microsoft/vscode-test-web/blob/main/CHANGELOG.md)
- [Commits](microsoft/vscode-test-web@v0.0.56...v0.0.65)

Updates `chai` from 4.5.0 to 5.1.2
- [Release notes](https://github.com/chaijs/chai/releases)
- [Changelog](https://github.com/chaijs/chai/blob/main/History.md)
- [Commits](chaijs/chai@v4.5.0...v5.1.2)

Updates `@types/chai` from 4.3.10 to 5.0.1
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/chai)

Updates `esbuild` from 0.23.1 to 0.24.0
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md)
- [Commits](evanw/esbuild@v0.23.1...v0.24.0)

Updates `mocha` from 10.8.2 to 11.0.1
- [Release notes](https://github.com/mochajs/mocha/releases)
- [Changelog](https://github.com/mochajs/mocha/blob/main/CHANGELOG.md)
- [Commits](mochajs/mocha@v10.8.2...v11.0.1)

Updates `msw` from 2.2.13 to 2.6.8
- [Release notes](https://github.com/mswjs/msw/releases)
- [Changelog](https://github.com/mswjs/msw/blob/main/CHANGELOG.md)
- [Commits](mswjs/msw@v2.2.13...v2.6.8)

---
updated-dependencies:
- dependency-name: "@types/node"
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: development-dependencies
- dependency-name: "@vscode/test-cli"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: development-dependencies
- dependency-name: "@vscode/test-web"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: development-dependencies
- dependency-name: chai
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: development-dependencies
- dependency-name: "@types/chai"
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: development-dependencies
- dependency-name: esbuild
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development-dependencies
- dependency-name: mocha
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: development-dependencies
- dependency-name: msw
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot requested a review from a team as a code owner December 9, 2024 17:21
@dependabot dependabot bot added the dependencies Auto-pinning label Dec 9, 2024
@jpogran
Copy link
Contributor

jpogran commented Dec 9, 2024

Chai v5 has moved to ESM only (this, among others), which does not work currently in the extension ecosystem. We will have to stay at 4.X for the time being

@jpogran
Copy link
Contributor

jpogran commented Dec 9, 2024

@dependabot ignore chai major version

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Dec 9, 2024

OK, I won't notify you about version 5.x.x of chai again, unless you unignore it.

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Dec 9, 2024

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

@dependabot dependabot bot closed this Dec 9, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/development-dependencies-1bf8b50905 branch December 9, 2024 19:32
@github-actions
Copy link

github-actions bot commented Jan 9, 2025

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 9, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Auto-pinning

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@jpogran