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.174.0 to 1.176.1

Release notes

Sourced from ts-proto's releases.

v1.176.1

1.176.1 (2024-05-25)

Bug Fixes

• camelToSnake to respect uppercase words, such as "GetAPIValue" -> "GET_API_VALUE" (#1046) (d2e75cd)

v1.176.0

1.176.0 (2024-05-16)

Features

• Bump ts-proto-descriptors to latest ts-proto. (#1043) (0b06554), closes #1042

v1.175.1

1.175.1 (2024-05-15)

Bug Fixes

• outputSchema=true when onlyTypes=true (#1039) (064665f)

v1.175.0

1.175.0 (2024-05-13)

Features

• optionally output versions used to generate files (#1040) (53d6799)

Changelog

Sourced from ts-proto's changelog.

1.176.1 (2024-05-25)

Bug Fixes

• camelToSnake to respect uppercase words, such as "GetAPIValue" -> "GET_API_VALUE" (#1046) (d2e75cd)

1.176.0 (2024-05-16)

Features

• Bump ts-proto-descriptors to latest ts-proto. (#1043) (0b06554), closes #1042

1.175.1 (2024-05-15)

Bug Fixes

• outputSchema=true when onlyTypes=true (#1039) (064665f)

1.175.0 (2024-05-13)

Features

• optionally output versions used to generate files (#1040) (53d6799)

Commits

• 63990c0 chore(release): 1.176.1 [skip ci]
• d2e75cd fix: camelToSnake to respect uppercase words, such as "GetAPIValue" -> "GET_A...
• 159c984 chore(release): 1.176.0 [skip ci]
• 0b06554 feat: Bump ts-proto-descriptors to latest ts-proto. (#1043)
• d0096d3 chore(release): 1.175.1 [skip ci]
• 064665f fix: outputSchema=true when onlyTypes=true (#1039)
• 23bb2f8 chore(release): 1.175.0 [skip ci]
• 53d6799 feat: optionally output versions used to generate files (#1040)
• See full diff in compare view

Updates @bufbuild/buf from 1.31.0 to 1.32.2

Release notes

Sourced from @​bufbuild/buf's releases.

v1.32.2

• Update buf generate to warn instead of error when proto3 optional is required but not supported by a plugin.

v1.32.1

• Fix archive and git inputs so that --path and --exclude-path paths are relative to the #subdir rather than the root of the input. This fixes an unintended behavior change that was introduced in v1.32.0.
• Add module input for protoc-gen-buf-lint and protoc-gen-buf-breaking to allow users to specify the module for v2 configuration files.

v1.32.0

This release contains the (completely backwards-compatible) next generation of the Buf CLI. The Buf CLI and its associated configuration have been completely overhauled to support monorepos as first-class citizens. We'd call it a v2 of buf, but it's not. Buf is enterprise-grade software, and we want you to be minimally impacted. The v1.32.0 release of buf introduces v2 config formats for both buf.yaml and buf.gen.yaml. All your current commands and v1 configuration continue to work, so you can upgrade to v2 configuration when appropriate.

To read more about what's new, check out our blog and our docs:

• Introducing the next generation of the Buf CLI: still v1 and backwards-compatible
• Introducing the newly improved BSR UI and buf push experience
• Migrate to v2 configuration files

---

• Add version v2 for buf.yaml and buf.gen.yaml configuration files.
• Add buf config migrate to migrate configuration files to the latest version (now v2).
• Move buf mod init to buf config init. buf mod init is now deprecated.
• Move buf mod ls-lint-rules to buf config ls-lint-rules. buf mod ls-lint-rules is now deprecated.
• Move buf mod ls-breaking-rules to buf config ls-breaking-rules. buf mod ls-breaking-rules is now deprecated.
• Move buf mod prune to buf dep prune. buf mod prune is now deprecated.
• Move buf mod update to buf dep update. buf mod update is now deprecated.
• Move buf mod {clear-cache,cc} to buf registry cc. buf mod {clear-cache,cc} is now deprecated.
• Move buf beta graph to stable as buf dep graph.
• Change the default visibility of buf push --create-visibility to private when the --create flag is set. Users are no longer required to set --create-visibility when running buf push --create.
• Add buf push --label, which allows users to set labels when pushing new commits to the BSR.
• Add buf push --source-control-url, which allows users to associate commits pushed to the BSR with a URL to a source code repository.
• Add buf push --create-default-label, which allows users to set a default label for a repository when calling buf push --create.
• Add buf push --git-metadata, which automatically sets appropriate --label, --source-control-url, and --create-default-label flags based on the current Git repository.
• Add buf convert --validate to apply protovalidate rules to incoming messages specified with --from.
• Deprecate buf mod open.
• Delete buf beta migrate-v1beta1 This is now replaced with buf config migrate.
• Add buf registry sdk version to get the version of a Generated SDK for a module and plugin.
• Add buf beta registry archive and buf beta registry unarchive commands for archiving and unarchiving labels on the BSR.
• Add support for Protobuf Editions. This allows buf to be used with sources that use edition 2023, instead of proto2 or proto3 syntax. This also updates the protoc-gen-buf-breaking and protoc-gen-buf-lint Protobuf plugins to support files that use edition 2023.
• Update buf breaking rules to work with Protobuf Editions. To support Editions, some rules have been deprecated and replaced with Editions-aware rules. All deprecated rules continue to work for existing users.
  • FIELD_SAME_CTYPE has been replaced with FIELD_SAME_CPP_STRING_TYPE, which considers both ctype field options and new (pb.cpp).string_type features when deciding on backwards compatibility.
  • FIELD_SAME_LABEL has been replaced with three rules that all check "cardinality". The new rules can distinguish between maps and other repeated fields and between implicit and explicit field presence. The new rules are:
    1. FIELD_SAME_CARDINALITY in the FILE and PACKAGE categories.
    2. FIELD_WIRE_COMPATIBLE_CARDINALITY in the WIRE category.
    3. FIELD_WIRE_JSON_COMPATIBLE_CARDINALITY in the WIRE_JSON category.
  • FILE_SAME_JAVA_STRING_CHECK_UTF8 has been replaced with FIELD_SAME_JAVA_UTF8_VALIDATION, which considers both the java_string_check_utf8 file option and (pb.java).utf8_validation features when deciding on backwards compatibility.
  • Add to the existing FILE_SAME_SYNTAX rule with a few related rules that can catch the same sort of compatibility issues, but in an Editions source file that changes feature values:
    1. MESSAGE_SAME_JSON_FORMAT and ENUM_SAME_JSON_FORMAT catch changes to the json_format feature, which controls whether support for the JSON format is best-effort or properly supported. When supported, the compiler performs more checks relating to field name collisions for the JSON format as well as for FieldMask usage.
    2. FIELD_SAME_UTF8_VALIDATION catches changes to the utf8_validation feature, which controls validation of string values.
    3. ENUM_SAME_TYPE catches changes to an enum's type, open vs. closed.
• Add support for extensions to buf breaking. All existing rules for fields are now applied to extensions, except for FIELD_NO_DELETE (and its variants). There are also new EXTENSION_NO_DELETE and PACKAGE_EXTENSION_NO_DELETE rules for catching deletions of an extension. The new rules are not active by default in existing v1 and v1beta1 configurations, for backwards-compatibility reasons. Migrate your config to v2 to use them.

... (truncated)

Changelog

Sourced from @​bufbuild/buf's changelog.

[v1.32.2] - 2024-05-28

• Update buf generate to warn instead of error when proto3 optional is required but not supported by a plugin.

[v1.32.1] - 2024-05-21

• Fix archive and git inputs so that --path and --exclude-path paths are relative to the #subdir rather than the root of the input. This fixes an unintended behavior change that was introduced in v1.32.0.
• Add module input for protoc-gen-buf-lint and protoc-gen-buf-breaking to allow users to specify the module for v2 configuration files.

[v1.32.0] - 2024-05-16

• Add version v2 for buf.yaml and buf.gen.yaml configuration files.
• Add buf config migrate to migrate configuration files to the latest version (now v2).
• Move buf mod init to buf config init. buf mod init is now deprecated.
• Move buf mod ls-lint-rules to buf config ls-lint-rules. buf mod ls-lint-rules is now deprecated.
• Move buf mod ls-breaking-rules to buf config ls-breaking-rules. buf mod ls-breaking-rules is now deprecated.
• Move buf mod prune to buf dep prune. buf mod prune is now deprecated.
• Move buf mod update to buf dep update. buf mod update is now deprecated.
• Move buf mod {clear-cache,cc} to buf registry cc. buf mod {clear-cache,cc} is now deprecated.
• Move buf beta graph to stable as buf dep graph.
• Change the default visibility of buf push --create-visibility to private when the --create flag is set. Users are no longer required to set --create-visibility when running buf push --create.
• Add buf push --label, which allows users to set labels when pushing new commits to the BSR.
• Add buf push --source-control-url, which allows users to associate commits pushed to the BSR with a URL to a source code repository.
• Add buf push --create-default-label, which allows users to set a default label for a repository when calling buf push --create.
• Add buf push --git-metadata, which automatically sets appropriate --label, --source-control-url, and --create-default-label flags based on the current Git repository.
• Add buf convert --validate to apply protovalidate rules to incoming messages specified with --from.
• Deprecate buf mod open.
• Delete buf beta migrate-v1beta1 This is now replaced with buf config migrate.
• Add buf registry sdk version to get the version of a Generated SDK for a module and plugin.
• Add buf beta registry archive and buf beta registry unarchive commands for archiving and unarchiving labels on the BSR.
• Add support for Protobuf Editions. This allows buf to be used with sources that use edition 2023, instead of proto2 or proto3 syntax. This also updates the protoc-gen-buf-breaking and protoc-gen-buf-lint Protobuf plugins to support files that use edition 2023.
• Update buf breaking rules to work with Protobuf Editions. To support Editions, some rules have been deprecated and replaced with Editions-aware rules. All deprecated rules continue to work for existing users.

... (truncated)

Commits

• 47016f1 Release v1.32.2 (#3028)
• 0be85d3 Warn when a plugin does not proto3 optional instead of error-ing (#3015)
• 2dfac93 Support annotated tags for push git metadata (#3013)
• 0ebe2de Fix link to tour (#3027)
• 3765c7d Bump alpine from 3.19.1 to 3.20.0 (#3018)
• bf54023 Bump bufbuild/buf-setup-action from 1.32.0 to 1.32.1 (#3017)
• 081013c Update buf generate long description (#3022)
• 90659b3 Make upgrade and upgrade dependencies (#3021)
• 1ff6e69 Avoid building image for buf export when --exclude-imports flag is set (#...
• 09ff5ec Bump buf.build/gen/go/bufbuild/registry/connectrpc/go from 1.16.1-20240514010...
• Additional commits viewable in compare view

Updates @types/node from 20.12.7 to 20.13.0

Commits

• See full diff in compare view

Updates esbuild from 0.20.2 to 0.21.4

Release notes

Sourced from esbuild's releases.

v0.21.4

• Update support for import assertions and import attributes in node (#3778)

  Import assertions (the assert keyword) have been removed from node starting in v22.0.0. So esbuild will now strip them and generate a warning with --target=node22 or above:

  ▲ [WARNING] The "assert" keyword is not supported in the configured target environment ("node22") [assert-to-with]
  example.mjs:1:40:
    1 │ import json from "esbuild/package.json" assert { type: "json" }
      │                                         ~~~~~~
      ╵                                         with
  
  Did you mean to use "with" instead of "assert"?
  

  Import attributes (the with keyword) have been backported to node 18 starting in v18.20.0. So esbuild will no longer strip them with --target=node18.N if N is 20 or greater.

• Fix for await transform when a label is present

  This release fixes a bug where the for await transform, which wraps the loop in a try statement, previously failed to also move the loop's label into the try statement. This bug only affects code that uses both of these features in combination. Here's an example of some affected code:

  // Original code
  async function test() {
    outer: for await (const x of [Promise.resolve([0, 1])]) {
      for (const y of x) if (y) break outer
      throw 'fail'
    }
  }
  // Old output (with --target=es6)
  function test() {
  return __async(this, null, function* () {
  outer: try {
  for (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp, error; more = !(temp = yield iter.next()).done; more = false) {
  const x = temp.value;
  for (const y of x) if (y) break outer;
  throw "fail";
  }
  } catch (temp) {
  error = [temp];
  } finally {
  try {
  more && (temp = iter.return) && (yield temp.call(iter));
  } finally {
  if (error)
  throw error[0];
  }
  }

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.21.4

• Update support for import assertions and import attributes in node (#3778)

  Import assertions (the assert keyword) have been removed from node starting in v22.0.0. So esbuild will now strip them and generate a warning with --target=node22 or above:

  ▲ [WARNING] The "assert" keyword is not supported in the configured target environment ("node22") [assert-to-with]
  example.mjs:1:40:
    1 │ import json from "esbuild/package.json" assert { type: "json" }
      │                                         ~~~~~~
      ╵                                         with
  
  Did you mean to use "with" instead of "assert"?
  

  Import attributes (the with keyword) have been backported to node 18 starting in v18.20.0. So esbuild will no longer strip them with --target=node18.N if N is 20 or greater.

• Fix for await transform when a label is present

  This release fixes a bug where the for await transform, which wraps the loop in a try statement, previously failed to also move the loop's label into the try statement. This bug only affects code that uses both of these features in combination. Here's an example of some affected code:

  // Original code
  async function test() {
    outer: for await (const x of [Promise.resolve([0, 1])]) {
      for (const y of x) if (y) break outer
      throw 'fail'
    }
  }
  // Old output (with --target=es6)
  function test() {
  return __async(this, null, function* () {
  outer: try {
  for (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp, error; more = !(temp = yield iter.next()).done; more = false) {
  const x = temp.value;
  for (const y of x) if (y) break outer;
  throw "fail";
  }
  } catch (temp) {
  error = [temp];
  } finally {
  try {
  more && (temp = iter.return) && (yield temp.call(iter));
  } finally {
  if (error)
  throw error[0];
  }

... (truncated)

Commits

• 67cbf87 publish 0.21.4 to npm
• 4ad11c3 fix #3639, fix #3646: pass with to onResolve
• 516ca31 fix #3343: allow bundle-internal string aliases
• 9e2f304 fix #3416, fix #3425: better enum constant folding
• 8f1faf7 implement late constant-folding for && || ??
• 7d50a50 implement late constant-folding of string enums
• 1b29ac7 fold equality checks after cross-module inlining
• d7a8bf3 formatting support for @position-try (for #3773)
• 5069410 fix #3778: import assertions/attributes for node
• 11d568c run make update-compat-table
• 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