Bump the ts-proto group in /impl/ts-proto with 4 updates

[dependabot]

Bumps the ts-proto group in /impl/ts-proto with 4 updates: ts-proto, @bufbuild/buf, @types/node and esbuild.

Updates ts-proto from 1.181.1 to 2.0.3

Release notes

Sourced from ts-proto's releases.

v2.0.3

2.0.3 (2024-08-21)

Bug Fixes

• Fix running yarn:test locally. (#1097) (30385ed)

v2.0.2

2.0.2 (2024-08-16)

Bug Fixes

• Fix version loading in new dist layout. (#1091) (f1c23d2)

v2.0.1

2.0.1 (2024-08-16)

Bug Fixes

• Fix build from typescript bump. (3ecd498)

v2.0.0

2.0.0 (2024-08-16)

v1.181.2

1.181.2 (2024-08-15)

Bug Fixes

• toJSON Function with removeEnumPrefix=true and unrecognizedEnumValue=0 Options (#1089) (2401490), closes #1086 #1086

Changelog

Sourced from ts-proto's changelog.

2.0.3 (2024-08-21)

Bug Fixes

• Fix running yarn:test locally. (#1097) (30385ed)

2.0.2 (2024-08-16)

Bug Fixes

• Fix version loading in new dist layout. (#1091) (f1c23d2)

2.0.1 (2024-08-16)

Bug Fixes

• Fix build from typescript bump. (3ecd498)

2.0.0 (2024-08-16)

1.181.2 (2024-08-15)

Bug Fixes

• toJSON Function with removeEnumPrefix=true and unrecognizedEnumValue=0 Options (#1089) (2401490), closes #1086 #1086

Commits

• 7b9a93b chore(release): 2.0.3 [skip ci]
• 30385ed fix: Fix running yarn:test locally. (#1097)
• 17edf89 Added generated client implementations (#1094)
• c4cfc90 chore(release): 2.0.2 [skip ci]
• f1c23d2 fix: Fix version loading in new dist layout. (#1091)
• 5e058bb docs: Add 2.x release notes.
• b65d40a chore(release): 2.0.1 [skip ci]
• 3ecd498 fix: Fix build from typescript bump.
• f9bd6d7 chore(release): 2.0.0 [skip ci]
• 3cf703d chore: Add the conventionalcommits plugin.
• Additional commits viewable in compare view

Updates @bufbuild/buf from 1.36.0 to 1.39.0

Release notes

Sourced from @​bufbuild/buf's releases.

v1.39.0

• Fix git input handling of relative HEAD refs without branch names.
• Add includes key to module configurations in v2 buf.yaml, accepting a list of directories.
  • If includes is specified, a proto file is considered in the module only if it is in one of the directories specified.
  • If both includes and excludes keys are specified for a module, a proto file is considered part of this module if it is contained in any of the include paths and not in any of the exclude paths.
• Allow multiple module configurations in the same v2 buf.yaml to have the same directory path.

v1.38.0

• Add --http3 flag to buf curl which forces buf curl to use HTTP/3 as the transport.
• Fix issue with directory inputs for v2 workspaces where the specified directory was not itself a path to a module, but contained directories with modules, and the modules would not build.
• Stop creating empty buf.lock files when buf dep update does not find new dependencies to update and there is no existing buf.lock.
• Update buf push to push the license file or doc file (e.g. README.md, LICENSE) in the same directory as buf.yaml if a module does not have a license file or doc file in the module's directory.
• Fix constraints of --path flag for lint and breaking rules to avoid resolving all files within a module. This change can result in a performance improvement for large workspaces.

v1.37.0

• Add STABLE_PACKAGE_NO_IMPORT_UNSTABLE lint rule which disallows files from stable packages to import files from unstable packages.
• Fix plugin push failures when pushing an image built with containerd image store.

Changelog

Sourced from @​bufbuild/buf's changelog.

[v1.39.0] - 2024-08-27

• Fix git input handling of relative HEAD refs without branch names.
• Add includes key to module configurations in v2 buf.yaml, accepting a list of directories.
  • If includes is specified, a proto file is considered in the module only if it is in one of the directories specified.
  • If both includes and excludes keys are specified for a module, a proto file is considered part of this module if it is contained in any of the include paths and not in any of the exclude paths.
• Allow multiple module configurations in the same v2 buf.yaml to have the same directory path.

[v1.38.0] - 2024-08-22

• Add --http3 flag to buf curl which forces buf curl to use HTTP/3 as the transport.
• Fix issue with directory inputs for v2 workspaces where the specified directory was not itself a path to a module, but contained directories with modules, and the modules would not build.
• Stop creating empty buf.lock files when buf dep update does not find new dependencies to update and there is no existing buf.lock.
• Update buf push to push the license file or doc file (e.g. README.md, LICENSE) in the same directory as buf.yaml if a module does not have a license file or doc file in the module's directory.
• Fix constraints of --path flag for lint and breaking rules to avoid resolving all files within a module. This change can result in a performance improvement for large workspaces.

[v1.37.0] - 2024-08-16

• Add STABLE_PACKAGE_NO_IMPORT_UNSTABLE lint rule which disallows files from stable packages to import files from unstable packages.
• Fix plugin push failures when pushing an image built with containerd image store.

Commits

• 496f588 Release v1.39.0 (#3272)
• 681874a Surface module description in command outputs and errors when possible (#3271)
• ba0fdb0 Add includes to v2 buf.yaml module config and allow duplicate module paths in...
• 64e1fa5 Fix git checkout for relative HEAD refs (#3266)
• 3857019 More issue template modifications (#3270)
• f1d577e More issue template modifications (#3269)
• e22893b Modify issue templates (#3268)
• d24a14d Make issue templates even stricter (#3267)
• 35adc2b Make upgrade (#3264)
• 8063ca9 Refactor bufprint package (#3173)
• Additional commits viewable in compare view

Updates @types/node from 22.0.2 to 22.5.1

Commits

• See full diff in compare view

Updates esbuild from 0.23.0 to 0.23.1

Release notes

Sourced from 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 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

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