Bump the ts-proto group across 1 directory with 5 updates

[dependabot]

Bumps the ts-proto group with 5 updates in the /impl/ts-proto directory:

Package	From	To
ts-proto	2.11.6	2.12.0
@bufbuild/buf	1.66.1	1.72.0
@types/node	25.5.0	26.1.2
esbuild	0.27.4	0.28.1
typescript	6.0.2	7.0.2

Updates ts-proto from 2.11.6 to 2.12.0

Release notes

Sourced from ts-proto's releases.

v2.12.0

2.12.0 (2026-07-03)

Features

• coerces bigint inputs inside fromPartial to bigint (#1266) (a89ddec), closes #1264

v2.11.10

2.11.10 (2026-06-30)

Bug Fixes

• incorrect codegen when grpc-js & outputSchema is used (#1262) (6ae3e40), closes #609
• Update js map check to include forceLong=bigInt as well (#1263) (1799765), closes #905 #940

v2.11.9

2.11.9 (2026-06-27)

Bug Fixes

• prevent code injection via string option/extension values in out… (#1261) (af15aff)

v2.11.8

2.11.8 (2026-05-07)

Bug Fixes

• precision and canonical form in useDuration=string Duration JSON helpers (#1257) (f31dada), closes #1176 #1176

v2.11.7

2.11.7 (2026-05-03)

Bug Fixes

• wrappers are not generated for nested google.protobuf.Timestamp and google.protobuf.Struct (#1254) (79b82f7)

Changelog

Sourced from ts-proto's changelog.

2.12.0 (2026-07-03)

Features

• coerces bigint inputs inside fromPartial to bigint (#1266) (a89ddec), closes #1264

2.11.10 (2026-06-30)

Bug Fixes

• incorrect codegen when grpc-js & outputSchema is used (#1262) (6ae3e40), closes #609
• Update js map check to include forceLong=bigInt as well (#1263) (1799765), closes #905 #940

2.11.9 (2026-06-27)

Bug Fixes

• prevent code injection via string option/extension values in out… (#1261) (af15aff)

2.11.8 (2026-05-07)

Bug Fixes

• precision and canonical form in useDuration=string Duration JSON helpers (#1257) (f31dada), closes #1176 #1176

2.11.7 (2026-05-03)

Bug Fixes

• wrappers are not generated for nested google.protobuf.Timestamp and google.protobuf.Struct (#1254) (79b82f7)

Commits

• cea02dd chore(release): 2.12.0 [skip ci]
• a89ddec feat: coerces bigint inputs inside fromPartial to bigint (#1266)
• e25dd9c docs: Update protobuf.js maintenance status (#1265)
• faaba11 chore(release): 2.11.10 [skip ci]
• 6ae3e40 fix: incorrect codegen when grpc-js & outputSchema is used (#1262)
• 1799765 fix: Update js map check to include forceLong=bigInt as well (#1263)
• 898251b chore(release): 2.11.9 [skip ci]
• af15aff fix: prevent code injection via string option/extension values in out… (#1261)
• 2666e55 chore(release): 2.11.8 [skip ci]
• f31dada fix: precision and canonical form in useDuration=string Duration JSON helpers...
• Additional commits viewable in compare view

Updates @bufbuild/buf from 1.66.1 to 1.72.0

Release notes

Sourced from @​bufbuild/buf's releases.

v1.72.0

• Fix buf beta registry webhook create and buf beta registry webhook list to emit proto JSON output.
• Fix HTTPS Basic authentication for remote inputs to use BUF_INPUT_HTTPS_USERNAME for the username.
• Fix IMPORT_USED lint rule silently reporting no unused imports when google/protobuf/descriptor.proto is in the transitive dependency graph.

v1.71.0

• Port new formatter and fix bugs for in-line block comment spacing.
• Fix handling for an empty rpc input/output.

v1.70.0

• Add LSP completion for buf.gen.yaml, buf.yaml, and buf.policy.yaml files.
• Fix LSP textDocument/documentSymbol marking every symbol as deprecated.
• Add error for when a dependency is added to buf.yaml and is missing from buf.lock.
• Update the PROTOVALIDATE lint rule support checking NaN in const, in, not_in, gt, gte, lt and lte rules for float and double fields.
• Update the PROTOVALIDATE lint rule support to check (buf.validate.message).oneof rules and make sure they are well-formed and valid.

v1.69.0

• Increase check plugin WASM memory limits to 1GiB.
• Fix LSP stale diagnostics persisting after a file is closed or deleted.
• Fix handling of unprefixed newlines in block comments.
• Add LSP code lenses for buf.gen.yaml files: "Run buf generate" and "Check for plugin updates".
• Add LSP warnings for lint.ignore and breaking.ignore paths in buf.yaml that do not match any file in the workspace.

v1.68.4

• Fix duplicated extension tags across imports from compiler.

v1.68.3

• Fix buf format error handling for edition 2024.

v1.68.2

• Fix build failures for modules with a vendored descriptor.proto.
• Fix LSP incorrectly reporting "edition '2024' not yet fully supported" errors.
• Fix CEL compilation error messages in buf lint to use the structured error API instead of parsing cel-go's text output.
• Add --debug-address flag to buf lsp serve to provide debug and profile support.

v1.68.1

• Revert the use of the new compiler report format and properly ungate Editions 2024 features.
• Fix absolute imports (leading-dot) marked unused in diagnostics.

v1.68.0

This release ports buf to our new Protobuf compiler, already used to power the Buf LSP. It uses a query-driven frontend and a new AST and intermediate representation, designed from the ground up to bring several improvements:

• Better diagnostics. The new compiler produces rich, structured diagnostic reports with precise source locations. It also catches issues that protoc misses, such as duplicate repeated modifiers.
• Editions 2024 support. Full support for Protobuf Editions 2024.
• Faster and more memory efficient. Designed for large workspaces, the new compiler uses less memory and compiles faster than the previous implementation.

This is a seamless upgrade for buf users: no changes are required, the output has been automatically updated to a new, richer diagnostics report.

---

... (truncated)

Changelog

Sourced from @​bufbuild/buf's changelog.

[v1.72.0] - 2026-07-17

• Fix buf beta registry webhook create and buf beta registry webhook list to emit proto JSON output.
• Fix HTTPS Basic authentication for remote inputs to use BUF_INPUT_HTTPS_USERNAME for the username.
• Fix IMPORT_USED lint rule silently reporting no unused imports when google/protobuf/descriptor.proto is in the transitive dependency graph.

[v1.71.0] - 2026-06-16

• Port new formatter and fix bugs for in-line block comment spacing.
• Fix handling for an empty rpc input/output.

[v1.70.0] - 2026-05-25

• Add LSP completion for buf.gen.yaml, buf.yaml, and buf.policy.yaml files.
• Fix LSP textDocument/documentSymbol marking every symbol as deprecated.
• Add error for when a dependency is added to buf.yaml and is missing from buf.lock.
• Update the PROTOVALIDATE lint rule support checking NaN in const, in, not_in, gt, gte, lt and lte rules for float and double fields.
• Update the PROTOVALIDATE lint rule support to check (buf.validate.message).oneof rules and make sure they are well-formed and valid.

[v1.69.0] - 2026-04-29

• Increase check plugin WASM memory limits to 1GiB.
• Fix LSP stale diagnostics persisting after a file is closed or deleted.
• Fix handling of unprefixed newlines in block comments.
• Add LSP code lenses for buf.gen.yaml files: "Run buf generate" and "Check for plugin updates".
• Add LSP warnings for lint.ignore and breaking.ignore paths in buf.yaml that do not match any file in the workspace.

[v1.68.4] - 2026-04-22

• Fix duplicated extension tags across imports from compiler.

[v1.68.3] - 2026-04-20

• Fix buf format error handling for edition 2024.

[v1.68.2] - 2026-04-17

• Fix build failures for modules with a vendored descriptor.proto.
• Fix LSP incorrectly reporting "edition '2024' not yet fully supported" errors.
• Fix CEL compilation error messages in buf lint to use the structured error API instead of parsing cel-go's text output.
• Add --debug-address flag to buf lsp serve to provide debug and profile support.

[v1.68.1] - 2026-04-14

• Revert the use of the new compiler report format and properly ungate Editions 2024 features.
• Fix absolute imports (leading-dot) marked unused in diagnostics.

... (truncated)

Commits

• 7d6f056 Release v1.72.0 (#4617)
• 46fa3e4 Make upgrade (#4616)
• efe167b Fix buf generate clean to not delete nested output (#4615)
• f6c012f Make upgrade (#4608)
• 67dfe4c Fix IMPORT_UNUSED when descriptor.proto is in the dependency graph (#4602)
• b518200 Fix HTTPS Basic auth for env variables (#4600)
• e2b3f44 Add recommended SDK added/removed audit events (#4601)
• 58b4fc0 Make upgrade (#4599)
• f0f8156 Fix webhook create/list output to use protojson (#4592)
• ce80ea7 Return to development (#4584)
• Additional commits viewable in compare view

Updates @types/node from 25.5.0 to 26.1.2

Commits

• See full diff in compare view

Updates esbuild from 0.27.4 to 0.28.1

Release notes

Sourced from esbuild's releases.

v0.28.1

• Disallow \ in local development server HTTP requests (GHSA-g7r4-m6w7-qqqr)

  This release fixes a security issue where HTTP requests to esbuild's local development server could traverse outside of the serve directory on Windows using a \ backslash character. It happened due to the use of Go's path.Clean() function, which only handles Unix-style / characters. HTTP requests with paths containing \ are no longer allowed.

  Thanks to @​dellalibera for reporting this issue.

• Add integrity checks to the Deno API (GHSA-gv7w-rqvm-qjhr)

  The previous release of esbuild added integrity checks to esbuild's npm install script. This release also adds integrity checks to esbuild's Deno install script. Now esbuild's Deno API will also fail with an error if the downloaded esbuild binary contains something other than the expected content.

  Note that esbuild's Deno API installs from registry.npmjs.org by default, but allows the NPM_CONFIG_REGISTRY environment variable to override this with a custom package registry. This change means that the esbuild executable served by NPM_CONFIG_REGISTRY must now match the expected content.

  Thanks to @​sondt99 for reporting this issue.

• Avoid inlining using and await using declarations (#4482)

  Previously esbuild's minifier sometimes incorrectly inlined using and await using declarations into subsequent uses of that declaration, which then fails to dispose of the resource correctly. This bug happened because inlining was done for let and const declarations by avoiding doing it for var declarations, which no longer worked when more declaration types were added. Here's an example:

  // Original code
  {
    using x = new Resource()
    x.activate()
  }
  // Old output (with --minify)
  new Resource().activate();
  // New output (with --minify)
  {using e=new Resource;e.activate()}

• Fix module evaluation when an error is thrown (#4461, #4467)

  If an error is thrown during module evaluation, esbuild previously didn't preserve the state of the module for subsequent module references. This was observable if import() or require() is used to import a module multiple times. The thrown error is supposed to be thrown by every call to import() or require(), not just the first. With this release, esbuild will now throw the same error every time you call import() or require() on a module that throws during its evaluation.

• Fix some edge cases around the new operator (#4477)

  Previously esbuild incorrectly printed certain edge cases involving complex expressions inside the target of a new expression (specifically an optional chain and/or a tagged template literal). The generated code for the new target was not correctly wrapped with parentheses, and either contained a syntax error or had different semantics. These edge cases have been fixed so that they now correctly wrap the new target in parentheses. Here is an example of some affected code:

  // Original code
  new (foo()`bar`)()
  new (foo()?.bar)()
  // Old output
  new foo()bar();
  new (foo())?.bar();

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.28.1

• Disallow \ in local development server HTTP requests (GHSA-g7r4-m6w7-qqqr)

  This release fixes a security issue where HTTP requests to esbuild's local development server could traverse outside of the serve directory on Windows using a \ backslash character. It happened due to the use of Go's path.Clean() function, which only handles Unix-style / characters. HTTP requests with paths containing \ are no longer allowed.

  Thanks to @​dellalibera for reporting this issue.

• Add integrity checks to the Deno API (GHSA-gv7w-rqvm-qjhr)

  The previous release of esbuild added integrity checks to esbuild's npm install script. This release also adds integrity checks to esbuild's Deno install script. Now esbuild's Deno API will also fail with an error if the downloaded esbuild binary contains something other than the expected content.

  Note that esbuild's Deno API installs from registry.npmjs.org by default, but allows the NPM_CONFIG_REGISTRY environment variable to override this with a custom package registry. This change means that the esbuild executable served by NPM_CONFIG_REGISTRY must now match the expected content.

  Thanks to @​sondt99 for reporting this issue.

• Avoid inlining using and await using declarations (#4482)

  Previously esbuild's minifier sometimes incorrectly inlined using and await using declarations into subsequent uses of that declaration, which then fails to dispose of the resource correctly. This bug happened because inlining was done for let and const declarations by avoiding doing it for var declarations, which no longer worked when more declaration types were added. Here's an example:

  // Original code
  {
    using x = new Resource()
    x.activate()
  }
  // Old output (with --minify)
  new Resource().activate();
  // New output (with --minify)
  {using e=new Resource;e.activate()}

• Fix module evaluation when an error is thrown (#4461, #4467)

  If an error is thrown during module evaluation, esbuild previously didn't preserve the state of the module for subsequent module references. This was observable if import() or require() is used to import a module multiple times. The thrown error is supposed to be thrown by every call to import() or require(), not just the first. With this release, esbuild will now throw the same error every time you call import() or require() on a module that throws during its evaluation.

• Fix some edge cases around the new operator (#4477)

  Previously esbuild incorrectly printed certain edge cases involving complex expressions inside the target of a new expression (specifically an optional chain and/or a tagged template literal). The generated code for the new target was not correctly wrapped with parentheses, and either contained a syntax error or had different semantics. These edge cases have been fixed so that they now correctly wrap the new target in parentheses. Here is an example of some affected code:

  // Original code
  new (foo()`bar`)()
  new (foo()?.bar)()
  // Old output
  new foo()bar();
  new (foo())?.bar();

... (truncated)

Commits

• bb9db84 publish 0.28.1 to npm
• 9ff053e security: add integrity checks to the Deno API
• 0a9bf21 enforce non-negative size in gzip parser
• e2a1a71 security: forbid \\ in local dev server requests
• 83a2cbf fix #4482: don't inline using declarations
• 308ad74 fix #4471: renaming of nested var declarations
• f013f5f fix some typos
• aafd6e4 chore: fix some minor issues in comments (#4462)
• 15300c3 follow up: cjs evaluation fixes
• 1bda0c3 fix #4461, fix #4467: esm evaluation fixes
• Additional commits viewable in compare view

Updates typescript from 6.0.2 to 7.0.2

Release notes

Sourced from typescript's releases.

TypeScript 6.0.3

For release notes, check out the release announcement blog post.

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).
• fixed issues query for TypeScript 6.0.2 (Stable).
• fixed issues query for TypeScript 6.0.3 (Stable).

Downloads are available on:

• npm

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for typescript since your current version.