search

Shopify / vscode-shopify-ruby

An opinionated and auto-configured set of extensions for Ruby development
MIT License
176 stars 13 forks source link

Bump the minor-and-patch group with 6 updates #615

Closed dependabot[bot] closed 3 months ago

dependabot[bot] commented 3 months ago

Bumps the minor-and-patch group with 6 updates:

Package From To
@types/node 20.14.9 20.14.10
@vscode/test-electron 2.4.0 2.4.1
esbuild 0.22.0 0.23.0
glob 10.4.2 10.4.3
mocha 10.5.2 10.6.0
typescript 5.5.2 5.5.3

Updates @types/node from 20.14.9 to 20.14.10

Commits


Updates @vscode/test-electron from 2.4.0 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.
Commits


Updates esbuild from 0.22.0 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>;

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>;

Commits


Updates glob from 10.4.2 to 10.4.3

Commits


Updates mocha from 10.5.2 to 10.6.0

Release notes

Sourced from mocha's releases.

v10.6.0

What's Changed

Full Changelog: https://github.com/mochajs/mocha/compare/v10.5.2...v10.6.0

Changelog

Sourced from mocha's changelog.

10.6.0 / 2024-07-02

:tada: Enhancements

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)
  • See full diff in compare view


Updates typescript from 5.5.2 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:

Commits


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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore 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 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 ` 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 ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions