Skip to content
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

Bump the minor-and-patch group across 1 directory with 11 updates #93

Closed
wants to merge 1 commit into from
Closed

Bump the minor-and-patch group across 1 directory with 11 updates #93

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Jul 15, 2024 •
edited
Loading

Bumps the minor-and-patch group with 11 updates in the /vscode directory:

Package From To
@babel/core 7.24.0 7.24.9
@types/node 20.11.22 20.14.10
@vscode/test-electron 2.3.9 2.4.1
@vscode/vsce 2.24.0 2.30.0
esbuild 0.20.1 0.23.0
mocha 10.3.0 10.6.0
@types/mocha 10.0.6 10.0.7
ovsx 0.8.3 0.9.1
prettier 3.2.5 3.3.3
typescript 5.3.3 5.5.3
vscode-textmate 9.0.0 9.1.0

Updates @babel/core from 7.24.0 to 7.24.9

Release notes

Sourced from @​babel/core's releases.

v7.24.9 (2024-07-15)

🐛 Bug Fix

💅 Polish

  • babel-generator, babel-plugin-transform-optional-chaining

🏠 Internal

  • babel-helper-module-transforms

Committers: 5

v7.24.8 (2024-07-11)

Thanks @​H0onnn, @​jkup and @​SreeXD for your first pull requests!

👓 Spec Compliance

🐛 Bug Fix

💅 Polish

... (truncated)

Changelog

Sourced from @​babel/core's changelog.

v7.24.9 (2024-07-15)

🐛 Bug Fix

💅 Polish

  • babel-generator, babel-plugin-transform-optional-chaining

🏠 Internal

  • babel-helper-module-transforms

v7.24.8 (2024-07-11)

👓 Spec Compliance

🐛 Bug Fix

💅 Polish

v7.24.7 (2024-06-05)

🐛 Bug Fix

🏠 Internal

... (truncated)

Commits

Updates @types/node from 20.11.22 to 20.14.10

Commits

Updates @vscode/test-electron from 2.3.9 to 2.4.1

Changelog

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

2.4.1 | 2024-07-05

  • Throw a typed TestRunFailedError on failure instead of a string.

2.4.0 | 2024-05-24

  • Allow installing unreleased builds using an -unreleased suffix, such as insiders-unreleased.
  • Allow passing different data directories in runVSCodeCommand, using it for extension development.
  • Improve the appearance progress reporting.

2.3.10 | 2024-05-13

  • Add runVSCodeCommand method and workaround for Node CVE-2024-27980
Commits

Updates @vscode/vsce from 2.24.0 to 2.30.0

Release notes

Sourced from @​vscode/vsce's releases.

v2.30.0

Changes:

Feature Requests:

  • #1009: Azure - create a custom chained token credential to place the AzureCLICredential prior to the ManagedIdentityCredential

Others:

  • #1011: Validate publisher on package
  • #1013: Print packaged files/folders

This list of changes was auto generated.

v2.29.1-2

Changes:

  • #1011: Validate publisher on package

This list of changes was auto generated.

v2.29.1-1

Changes:

  • #1013: Print packaged files/folders

This list of changes was auto generated.

v2.29.1-0

Changes:

Feature Requests:

  • #1009: Azure - create a custom chained token credential to place the AzureCLICredential prior to the ManagedIdentityCredential

This list of changes was auto generated.

... (truncated)

Commits

Updates esbuild from 0.20.1 to 0.23.0

Release notes

Sourced from esbuild's releases.

v0.23.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.22.0 or ~0.22.0. See npm's documentation about semver for more information.

  • Revert the recent change to avoid bundling dependencies for node (#3819)

    This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.

    I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.

    In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.

  • Fix preserving collapsed JSX whitespace (#3818)

    When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with --jsx=preserve. Here is an example:

    // Original code
<Foo>
  <Bar />
</Foo>
// Old output (with --jsx=preserve)
<Foo><Bar /></Foo>;
// New output (with --jsx=preserve)
<Foo>
<Bar />
</Foo>;

v0.22.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.21.0 or ~0.21.0. See npm's documentation about semver for more information.

  • Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)

    This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.

    With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.

    The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).

  • Drop support for older platforms (#3802)

    This release drops support for the following operating systems:

    • Windows 7
    • Windows 8
    • Windows Server 2008
    • Windows Server 2012

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.23.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.22.0 or ~0.22.0. See npm's documentation about semver for more information.

  • Revert the recent change to avoid bundling dependencies for node (#3819)

    This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.

    I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.

    In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.

  • Fix preserving collapsed JSX whitespace (#3818)

    When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with --jsx=preserve. Here is an example:

    // Original code
<Foo>
  <Bar />
</Foo>
// Old output (with --jsx=preserve)
<Foo><Bar /></Foo>;
// New output (with --jsx=preserve)
<Foo>
<Bar />
</Foo>;

0.22.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.21.0 or ~0.21.0. See npm's documentation about semver for more information.

  • Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)

    This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.

    With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.

    The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).

  • Drop support for older platforms (#3802)

    This release drops support for the following operating systems:

    • Windows 7
    • Windows 8
    • Windows Server 2008

... (truncated)

Commits

Updates mocha from 10.3.0 to 10.6.0

Release notes

Sourced from mocha's releases.

v10.6.0

What's Changed

Full Changelog: mochajs/mocha@v10.5.2...v10.6.0

v10.5.2

What's Changed

New Contributors

Full Changelog: mochajs/mocha@v10.5.1...v10.5.2

v10.5.1

What's Changed

New Contributors

Full Changelog: mochajs/mocha@v10.5.0...v10.5.1

v10.5.0

🎉 Enhancements

🐛 Fixes

🔩 Other

v10.4.0

10.4.0 / 2024-03-26

... (truncated)

Changelog

Sourced from mocha's changelog.

10.6.0 / 2024-07-02

🎉 Enhancements

10.5.2 / 2024-06-25

🐛 Fixes

10.5.1 / 2024-06-24

🐛 Fixes

  • #5086 fix: Add error handling for nonexistent file case with --file option (@​khoaHyh)

10.5.0 / 2024-06-24

🎉 Enhancements

🐛 Fixes

🔩 Other

10.4.0 / 2024-03-26

🎉 Enhancements

🐛 Fixes

... (truncated)

Commits
  • 177732f Release 10.6.0
  • 021aa80 docs: add 10.6.0 to CHANGELOG.md
  • 528836e docs: fix month numbers in CHANGELOG.md
  • bb8d7b9 feat: allow ^ versions for miscellaneous packages (#5154)
  • 514b83f feat: allow ^ versions for data serialization packages (#5153)
  • be82606 feat: allow ^ versions for file matching packages (#5151)
  • 71e9fba feat: allow ^ versions for yargs packages (#5152)
  • 38695da feat: allow ^ versions for character encoding packages (#5150)
  • b2a6358 Release 10.5.2
  • a3bb86d docs: add 10.5.2 to CHANGELOG.md
  • Additional commits viewable in compare view

Updates @types/mocha from 10.0.6 to 10.0.7

Commits

Updates ovsx from 0.8.3 to 0.9.1

Release notes

Sourced from ovsx's releases.

Open VSX v0.9.1

This is the fifth release of Open VSX. It consists of

Deploying the server application is documented in the Wiki.

What's Changed

Full Changelog: eclipse/openvsx@v0.9.0...v0.9.1

Open VSX v0.9.0

This is the fourth release of Open VSX. It consists of

Deploying the server application is documented in the Wiki.

What's Changed

... (truncated)

Changelog

Sourced from ovsx's changelog.

v0.9.1 (Apr. 2024)

Bug Fixes

Dependencies

  • Upgrade @vscode/vsce from 2.24.0 to 2.25.0 (#896)
  • Upgrade tar from 6.2.0 to 6.2.1 (#893)

v0.9.0 (Mar. 2024)

Breaking Changes

  • The minimum version of Node.js required is now 18 because of the newer @vscode/vsce

Dependencies

  • Upgrade @vscode/vsce from 2.19.0 to 2.24.0 (#878)
  • Upgrade semver from 7.5.2 to 7.6.0 (#878)

v0.8.4 (Mar. 2024)

Dependencies

  • Upgrade follow-redirects from 1.14.8 to 1.15.6 (#869)
  • Upgrade ip from 2.0.0 to 2.0.1 (#858)
Commits

Updates prettier from 3.2.5 to 3.3.3

Release notes

Sourced from prettier's releases.

3.3.3

🔗 Changelog

3.3.2

🔗 Changelog

3.3.1

🔗 Changelog

3.3.0

diff

🔗 Release note

Changelog

Sourced from prettier's changelog.

3.3.3

diff

Add parentheses for nullish coalescing in ternary (#16391 by @​cdignam-segment)

This change adds clarity to operator precedence.

// Input
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;
// Prettier 3.3.2
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;
// Prettier 3.3.3
foo ? (bar ?? foo) : baz;
(foo ?? bar) ? a : b;
a ? b : (foo ?? bar);

Add parentheses for decorator expressions (#16458 by @​y-schneider)

Prevent parentheses around member expressions or tagged template literals from being removed to follow the stricter parsing rules of TypeScript 5.5.

// Input
@(foo`tagged template`)
class X {}
// Prettier 3.3.2
@​footagged template
class X {}
// Prettier 3.3.3
@(footagged template)
class X {}

Support @let declaration syntax (#16474 by @​sosukesuzuki)

Adds support for Angular v18 @let declaration syntax.

Please see the following code example. The @let declaration allows you to define local variables within the template:

... (truncated)

Commits

Updates typescript from 5.3.3 to 5.5.3

Release notes

Sourced from typescript's releases.

TypeScript 5.5.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

TypeScript 5.5

For release notes, ...

Description has been truncated

@dependabot
Bump the minor-and-patch group across 1 directory with 11 updates
92c6756 
Bumps the minor-and-patch group with 11 updates in the /vscode directory:

| Package | From | To |
| --- | --- | --- |
| [@babel/core](https://github.com/babel/babel/tree/HEAD/packages/babel-core) | `7.24.0` | `7.24.9` |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `20.11.22` | `20.14.10` |
| [@vscode/test-electron](https://github.com/Microsoft/vscode-test) | `2.3.9` | `2.4.1` |
| [@vscode/vsce](https://github.com/Microsoft/vsce) | `2.24.0` | `2.30.0` |
| [esbuild](https://github.com/evanw/esbuild) | `0.20.1` | `0.23.0` |
| [mocha](https://github.com/mochajs/mocha) | `10.3.0` | `10.6.0` |
| [@types/mocha](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/mocha) | `10.0.6` | `10.0.7` |
| [ovsx](https://github.com/eclipse/openvsx/tree/HEAD/cli) | `0.8.3` | `0.9.1` |
| [prettier](https://github.com/prettier/prettier) | `3.2.5` | `3.3.3` |
| [typescript](https://github.com/Microsoft/TypeScript) | `5.3.3` | `5.5.3` |
| [vscode-textmate](https://github.com/microsoft/vscode-textmate) | `9.0.0` | `9.1.0` |



Updates `@babel/core` from 7.24.0 to 7.24.9
- [Release notes](https://github.com/babel/babel/releases)
- [Changelog](https://github.com/babel/babel/blob/main/CHANGELOG.md)
- [Commits](https://github.com/babel/babel/commits/v7.24.9/packages/babel-core)

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

Updates `@vscode/test-electron` from 2.3.9 to 2.4.1
- [Changelog](https://github.com/microsoft/vscode-test/blob/main/CHANGELOG.md)
- [Commits](microsoft/vscode-test@v2.3.9...v2.4.1)

Updates `@vscode/vsce` from 2.24.0 to 2.30.0
- [Release notes](https://github.com/Microsoft/vsce/releases)
- [Commits](microsoft/vscode-vsce@v2.24.0...v2.30.0)

Updates `esbuild` from 0.20.1 to 0.23.0
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md)
- [Commits](evanw/esbuild@v0.20.1...v0.23.0)

Updates `mocha` from 10.3.0 to 10.6.0
- [Release notes](https://github.com/mochajs/mocha/releases)
- [Changelog](https://github.com/mochajs/mocha/blob/main/CHANGELOG.md)
- [Commits](mochajs/mocha@v10.3.0...v10.6.0)

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

Updates `ovsx` from 0.8.3 to 0.9.1
- [Release notes](https://github.com/eclipse/openvsx/releases)
- [Changelog](https://github.com/eclipse/openvsx/blob/master/cli/CHANGELOG.md)
- [Commits](https://github.com/eclipse/openvsx/commits/v0.9.1/cli)

Updates `prettier` from 3.2.5 to 3.3.3
- [Release notes](https://github.com/prettier/prettier/releases)
- [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md)
- [Commits](prettier/prettier@3.2.5...3.3.3)

Updates `typescript` from 5.3.3 to 5.5.3
- [Release notes](https://github.com/Microsoft/TypeScript/releases)
- [Changelog](https://github.com/microsoft/TypeScript/blob/main/azure-pipelines.release.yml)
- [Commits](microsoft/TypeScript@v5.3.3...v5.5.3)

Updates `vscode-textmate` from 9.0.0 to 9.1.0
- [Release notes](https://github.com/microsoft/vscode-textmate/releases)
- [Commits](https://github.com/microsoft/vscode-textmate/commits/v9.1.0)

---
updated-dependencies:
- dependency-name: "@babel/core"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: "@types/node"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: "@vscode/test-electron"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: "@vscode/vsce"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: esbuild
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: mocha
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: "@types/mocha"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: ovsx
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: prettier
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: typescript
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: vscode-textmate
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies javascript Pull requests that update Javascript code labels Jul 15, 2024
@dependabot Dependabot
Copy link
Author

dependabot bot commented on behalf of github Jul 15, 2024

Dependabot tried to add @andyw8/ruby-dev-exp as a reviewer to this PR, but received the following error from GitHub:

POST https://api.github.com/repos/andyw8/ruby-lsp/pulls/93/requested_reviewers: 422 - Reviews may only be requested from collaborators. One or more of the teams you specified is not a collaborator of the andyw8/ruby-lsp repository. // See: https://docs.github.com/rest/pulls/review-requests#request-reviewers-for-a-pull-request

@dependabot Dependabot
Copy link
Author

dependabot bot commented on behalf of github Jul 22, 2024

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

@dependabot dependabot bot closed this Jul 22, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/vscode/minor-and-patch-a5d2db7c61 branch July 22, 2024 12:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies javascript Pull requests that update Javascript code
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants