search

FriendsOfShopware / shopware-cli

CLI for Shopware Account and Shopware 6
MIT License
81 stars 31 forks source link

fix(deps): bump the all group with 4 updates #362

Closed dependabot[bot] closed 3 months ago

dependabot[bot] commented 3 months ago

Bumps the all group with 4 updates: github.com/evanw/esbuild, github.com/sashabaranov/go-openai, github.com/tetratelabs/wazero and golang.org/x/net.

Updates github.com/evanw/esbuild from 0.20.2 to 0.21.2

Release notes

Sourced from github.com/evanw/esbuild's releases.

v0.21.2

  • Correct this in field and accessor decorators (#3761)

    This release changes the value of this in initializers for class field and accessor decorators from the module-level this value to the appropriate this value for the decorated element (either the class or the instance). It was previously incorrect due to lack of test coverage. Here's an example of a decorator that doesn't work without this change:

    const dec = () => function() { this.bar = true }
class Foo { @dec static foo }
console.log(Foo.bar) // Should be "true"

  • Allow es2023 as a target environment (#3762)

    TypeScript recently added es2023 as a compilation target, so esbuild now supports this too. There is no difference between a target of es2022 and es2023 as far as esbuild is concerned since the 2023 edition of JavaScript doesn't introduce any new syntax features.

v0.21.1

  • Fix a regression with --keep-names (#3756)

    The previous release introduced a regression with the --keep-names setting and object literals with get/set accessor methods, in which case the generated code contained syntax errors. This release fixes the regression:

    // Original code
x = { get y() {} }

    // Output from version 0.21.0 (with --keep-names)
x = { get y: /* @PURE */ __name(function() {
}, "y") };
    

    // Output from this version (with --keep-names)
x = { get y() {
} };

v0.21.0

This release doesn't contain any deliberately-breaking changes. However, it contains a very complex new feature and while all of esbuild's tests pass, I would not be surprised if an important edge case turns out to be broken. So I'm releasing this as a breaking change release to avoid causing any trouble. As usual, make sure to test your code when you upgrade.

  • Implement the JavaScript decorators proposal (#104)

    With this release, esbuild now contains an implementation of the upcoming JavaScript decorators proposal. This is the same feature that shipped in TypeScript 5.0 and has been highly-requested on esbuild's issue tracker. You can read more about them in that blog post and in this other (now slightly outdated) extensive blog post here: https://2ality.com/2022/10/javascript-decorators.html. Here's a quick example:

    const log = (fn, context) => function() {
  console.log(`before ${context.name}`)
  const it = fn.apply(this, arguments)
  console.log(`after ${context.name}`)
  return it
}

    class Foo {
@​log static foo() {

... (truncated)

Changelog

Sourced from github.com/evanw/esbuild's changelog.

0.21.2

  • Correct this in field and accessor decorators (#3761)

    This release changes the value of this in initializers for class field and accessor decorators from the module-level this value to the appropriate this value for the decorated element (either the class or the instance). It was previously incorrect due to lack of test coverage. Here's an example of a decorator that doesn't work without this change:

    const dec = () => function() { this.bar = true }
class Foo { @dec static foo }
console.log(Foo.bar) // Should be "true"

  • Allow es2023 as a target environment (#3762)

    TypeScript recently added es2023 as a compilation target, so esbuild now supports this too. There is no difference between a target of es2022 and es2023 as far as esbuild is concerned since the 2023 edition of JavaScript doesn't introduce any new syntax features.

0.21.1

  • Fix a regression with --keep-names (#3756)

    The previous release introduced a regression with the --keep-names setting and object literals with get/set accessor methods, in which case the generated code contained syntax errors. This release fixes the regression:

    // Original code
x = { get y() {} }

    // Output from version 0.21.0 (with --keep-names)
x = { get y: /* @PURE */ __name(function() {
}, "y") };
    

    // Output from this version (with --keep-names)
x = { get y() {
} };

0.21.0

This release doesn't contain any deliberately-breaking changes. However, it contains a very complex new feature and while all of esbuild's tests pass, I would not be surprised if an important edge case turns out to be broken. So I'm releasing this as a breaking change release to avoid causing any trouble. As usual, make sure to test your code when you upgrade.

  • Implement the JavaScript decorators proposal (#104)

    With this release, esbuild now contains an implementation of the upcoming JavaScript decorators proposal. This is the same feature that shipped in TypeScript 5.0 and has been highly-requested on esbuild's issue tracker. You can read more about them in that blog post and in this other (now slightly outdated) extensive blog post here: https://2ality.com/2022/10/javascript-decorators.html. Here's a quick example:

    const log = (fn, context) => function() {
  console.log(`before ${context.name}`)
  const it = fn.apply(this, arguments)
  console.log(`after ${context.name}`)
  return it
}

... (truncated)

Commits


Updates github.com/sashabaranov/go-openai from 1.23.0 to 1.23.1

Release notes

Sourced from github.com/sashabaranov/go-openai's releases.

v1.23.1

What's Changed

New Contributors

Full Changelog: https://github.com/sashabaranov/go-openai/compare/v1.23.0...v1.23.1

Commits


Updates github.com/tetratelabs/wazero from 1.7.1 to 1.7.2

Release notes

Sourced from github.com/tetratelabs/wazero's releases.

v1.7.2

Hi all, another release for wazero has arrived! This v1.7.2 is just as boring as the previous v1.7.1, but includes important bug fixes!

Notably,

  • On amd64, wazero properly saves the potentially clobbered registers during memory.{copy,init,fill} instructions after #2202, by @​mathetake.
  • For very large stack traces with lots of inlined function calls, previously it included the omitted frames... comment in the wrong position, which is fixed in #2199 by @​mathetake.
  • A race condition during the concurrent compilation has been fixed in #2194 by @​mathetake
  • The custom memory allocator introduced in v1.7.1 has been fixed and now sets the memory capacity properly in #2189 by @​anuraaga

Enjoy! 👯 🕺 💃

Commits
  • 5a8a053 Merges interpreter and wazeroir packages (#2204)
  • bc0915e integration test: adds memmov regression tests (#2203)
  • 3403dd3 amd64: saves clobbered xmm8-xmm15 beyond runtime.memmove (#2202)
  • bac8bd1 fuzz: adds regression case for #2198 (#2201)
  • b7df8b1 debug: do not include inlined sources in frame counts (#2199)
  • 60dbe96 Assumes ctx is not nil (#2196)
  • 1e6080a compiler: uses slice instead of map for refToBinaryOffset (#2195)
  • 621f62d Fixes race condition in concurrent engine usage (#2194)
  • 7ad2b70 Removes GOOS=js related leftovers (#2193)
  • 5a9cb5a experimental: reflect custom allocated buffer capacity to internal buffer (#2...
  • Additional commits viewable in compare view


Updates golang.org/x/net from 0.24.0 to 0.25.0

Commits
  • d27919b go.mod: update golang.org/x dependencies
  • e0324fc http2: use net.ErrClosed
  • b20cd59 quic: initiate key rotation earlier in connections
  • f95a3b3 html: fix typo in package doc
  • 0a24555 http/httpguts: speed up ValidHeaderFieldName
  • ec05fdc http2: don't retry the first request on a connection on GOAWAY error
  • b67a0f0 http2: send correct LastStreamID in stream-caused GOAWAY
  • a130fcc quic: don't consider goroutines running when tests start as leaked
  • See full diff 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 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