Chore: bump google.golang.org/protobuf from 1.27.1 to 1.28.0

[dependabot[bot]]

Bumps google.golang.org/protobuf from 1.27.1 to 1.28.0.

Release notes

Sourced from google.golang.org/protobuf's releases.

v1.28.0

• Overview
• Notable changes
  • UnmarshalOption RecursionLimit
• Upcoming breakage changes

Overview

The release provides a new unmarshal option for limiting the recursion depth when unmarshalling nested messages to prevent stack overflows. (UnmarshalOptions.RecursionLimit).

Notable changes

New features:

• CL/340489: testing/protocmp: add Message.Unwrap

Documentation improvements:

• CL/339569: reflect/protoreflect: add more docs on Value aliasing

Updated supported versions:

• CL/370055: all: update supported versions

UnmarshalOption RecursionLimit

• CL/385854: all: implement depth limit for unmarshalling

The new UnmarshalOptions.RecursionLimit limits the maximum recursion depth when unmarshalling messages. The limit is applied for nested messages. When messages are nested deeper than the specified limit the unmarshalling will fail. If unspecified, a default limit of 10,000 is applied.

In addition to the configurable limit for message nesting a non-configurable recursion limit for group nesting of 10,000 was introduced.

Upcoming breakage changes

The default recursion limit of 10,000 introduced in the release is subject to change. We want to align this limit with implementations for other languages in the long term. C++ and Java use a limit of 100 which is also the target for the Go implementation.

Commits

• 32051b4 all: release v1.28.0
• 3992ea8 all: implement depth limit for unmarshaling
• e5db296 all: update supported versions
• 3a9e1dc all: gofmt all
• 26e8bcb all: remove unnecessary string([]byte) conversion in fmt.Sprintf with %s
• 5aec41b testing/protocmp: add Message.Unwrap
• 05be61f reflect/protoreflect: add more docs on Value aliasing
• b03064a all: start v1.27.1-devel
• 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 ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.