search

FriendsOfShopware / shopware-cli

CLI for Shopware Account and Shopware 6
MIT License
84 stars 32 forks source link

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

Closed dependabot[bot] closed 3 months ago

dependabot[bot] commented 3 months ago

Bumps the all group with 4 updates: dario.cat/mergo, github.com/evanw/esbuild, github.com/sashabaranov/go-openai and github.com/tetratelabs/wazero.

Updates dario.cat/mergo from 1.0.0 to 1.0.1

Release notes

Sourced from dario.cat/mergo's releases.

v1.0.1

What's Changed

New Contributors

Full Changelog: https://github.com/darccio/mergo/compare/v1.0.0...v1.0.1

Commits


Updates github.com/evanw/esbuild from 0.23.0 to 0.23.1

Release notes

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

v0.23.1

  • Allow using the node: import prefix with es* targets (#3821)

    The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

    // Original code
import fs from 'node:fs'
fs.open

    // Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
    
import fs from "fs";
    
fs.open;
    

    // New output (with --bundle --format=esm --platform=node --target=node18,es2022)
    
import fs from "node:fs";
    
fs.open;

  • Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

    Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

  • Fix incorrect location of certain error messages (#3845)

    This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

  • Print comments before case clauses in switch statements (#3838)

    With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

  • Fix a memory leak with pluginData (#3825)

    With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

Changelog

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

0.23.1

  • Allow using the node: import prefix with es* targets (#3821)

    The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

    // Original code
import fs from 'node:fs'
fs.open

    // Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
    
import fs from "fs";
    
fs.open;
    

    // New output (with --bundle --format=esm --platform=node --target=node18,es2022)
    
import fs from "node:fs";
    
fs.open;

  • Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

    Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

  • Fix incorrect location of certain error messages (#3845)

    This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

  • Print comments before case clauses in switch statements (#3838)

    With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

  • Fix a memory leak with pluginData (#3825)

    With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

Commits


Updates github.com/sashabaranov/go-openai from 1.28.1 to 1.28.2

Release notes

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

v1.28.2

What's Changed

New Contributors

Full Changelog: https://github.com/sashabaranov/go-openai/compare/v1.28.1...v1.28.2

Commits


Updates github.com/tetratelabs/wazero from 1.7.3 to 1.8.0

Release notes

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

v1.8.0

Hi wazero friends, been a while! The new release of wazero v1.8.0 has arrived 🎉 🏝️☀️ 🍺

This release has happened intentionally right after the Go 1.23 release. @​ncruces worked so hard (#2301), and updated our codebase to make it up-to-date with the new Go versions. Notably, since this release, we set our floor Go version to 1.21 (-2 from the latest) following our support policy.

The following is the brief summary of what's included in this release!

Experimental feature: importResolver

A new wazero friend @​bep from the Hugo community came up with an exciting way to "link" modules dynamically/anonymously, which we call "ImportResolver". The feature was implemented in #2298, and available under experimental package. If you are interested please give it a shot, and give us your feedback!

Emscripten update

@​jerbob92 found out that a breaking change was introduced in Emscripten 3.1.57+, and worked to make our emscripten package to support these recent versions. Unfortunately, the older emscriptens are not supported anymore, so users are encouraged to update their Emscripten version. #2290

Bug fixes

Compilation perf improvements

Just like the recent previous releases, @​mathetake worked hard to make compilation faster. Unfortunately, we don't have a concrete number to showcase here, but both Interpreter and Compiler engines now runs really faster compared to the previous releases during compilation without affecting the runtime performance.

If you are interested in the latest updates and discussion around this topic, feel free to follow the thread in #2182.

Others

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