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

[dependabot]

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

• fixes issue #187 by @​vsemichev in darccio/mergo#253
• fix: WithoutDereference should respect non-nil struct pointers by @​joshkaplinsky in darccio/mergo#251

New Contributors

• @​vsemichev made their first contribution in darccio/mergo#253
• @​joshkaplinsky made their first contribution in darccio/mergo#251

Full Changelog: darccio/mergo@v1.0.0...v1.0.1

Commits

• 59ea6a9 Merge pull request #251 from joshkaplinsky/joshkaplinsky/without-dereference-...
• 96f24af Merge pull request #253 from vsemichev/master
• 2f1a615 fixes issue #187. adds test to verify the fix.
• 4da170b fixes issue #187. attempt #3
• a13a117 fixes issue #187. attempt #2
• 6b830ff fixes issue #187
• f33862a WithoutDereference should respect structs
• cde9f0e Merge pull request #246 from darccio/darccio/v1-frozen
• f1e2fe5 chore: frozen v1
• 7f7b4af Update FUNDING.yml
• Additional commits viewable in compare view

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

• 3327274 publish 0.23.1 to npm
• 38e22ed add a warning/debug log message for #3867
• a15bb51 fix #3825: memory leak of pluginData values
• f6e6481 fix #3838: print comments before case clauses
• 9c13ae1 fix #3853: update go 1.22.4 => 1.22.5
• 78f89e4 fix #3845: some incorrect error message locations
• 892d2a7 fix #3834: cli sometimes panics with --analyze
• 360d472 fix a typo in the release notes
• e3f4e2d fix #3821: allow node: prefix with es* targets
• See full diff in compare view

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

• Run integration tests for PRs by @​HaraldNordgren in sashabaranov/go-openai#823
• feat: Completion request support seed by @​eiixy in sashabaranov/go-openai#800
• fix: fullURL endpoint generation by @​eiixy in sashabaranov/go-openai#817
• Allow structured outputs via function calling by @​greysteil in sashabaranov/go-openai#828

New Contributors

• @​HaraldNordgren made their first contribution in sashabaranov/go-openai#823

Full Changelog: sashabaranov/go-openai@v1.28.1...v1.28.2

Commits

• d86425a Allow structured outputs via function calling (#828)
• dd7f582 fix: fullURL endpoint generation (#817)
• 2c6889e fix: #788 (#800)
• 1880333 Run integration tests for PRs (#823)
• See full diff in compare view

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

• threads: lock around invocations of memory.Grow (#2279) @​anuraaga
• amd64: fixes lowerSqmulRoundSat (#2260) @​mathetake

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

• Update Benthos to Redpanda Connect (#2291) @​rockwotj

Commits

• 5ed4c17 ci: upgrade to Go 1.23 (#2301)
• 2b12e18 Improves ImportResolver example (#2299)
• a186448 Add experimental ImportResolver (#2298)
• 5ad3f06 doc: adds comments on simultaneous compilation (#2295)
• 22b92a5 Update Benthos to Redpanda Connect (#2291)
• c345ddf Add support for Emscripten version 3.1.57 (#2290)
• c077eab ci: tests with Go 1.23rc2 (#2277)
• 9a19a04 backend: stop allocating ValueDefinitions (#2288)
• e2db5ac backend: removes unnecessary ValueDefinition fields (#2287)
• 2c53c6b ssa: removes valueIDToInstruction slice (#2286)
• 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