fix(deps): update dependency @bufbuild/protobuf to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@bufbuild/protobuf (source)	^1.10.0 -> ^2.0.0

---

Release Notes

bufbuild/protobuf-es (@​bufbuild/protobuf)

v2.2.0

Compare Source

What's Changed

• Properly reset BinaryWriter after finish by @​bhollis in https://github.com/bufbuild/protobuf-es/pull/986
• Add typed DescMethod variants by @​srikrsna-buf in https://github.com/bufbuild/protobuf-es/pull/985

New Contributors

• @​bhollis made their first contribution in https://github.com/bufbuild/protobuf-es/pull/986

Full Changelog: bufbuild/protobuf-es@v2.1.0...v2.2.0

v2.1.0

Compare Source

What's Changed

• Fix assignability of wrong message type in create by @​timostamm in https://github.com/bufbuild/protobuf-es/pull/972
• Generate full JSDoc for JSON types by @​timostamm in https://github.com/bufbuild/protobuf-es/pull/975

Full Changelog: bufbuild/protobuf-es@v2.0.0...v2.1.0

v2.0.0

Compare Source

What's new in version 2

To support Protobuf editions, we have to make breaking changes that also affect users of proto2 and proto3. This prompted us to make more extensive changes that take feedback from version 1 into account:

We no longer use classes. Instead, we generate a schema object and a type for every message. To create a new instance, to serialize, and for other concerns, we provide functions. Here is a simple example:

import { create, toBinary } from "@​bufbuild/protobuf";
import { UserSchema } from "./gen/example_pb";

let user = create(UserSchema, {
  firstName: "Homer",
  lastName: "Simpson",
  active: true,
});

const bytes = toBinary(UserSchema, user);

If you use proto3, messages are now plain objects. Files with proto2 and editions use the prototype chain to track field presence.

This approach solves several outstanding issues, such as:

• https://github.com/bufbuild/protobuf-es/issues/397 Provide custom options at runtime
• https://github.com/bufbuild/protobuf-es/issues/551 Generated types allow assigning wrong message type if it is a superset of the target type
• https://github.com/bufbuild/protobuf-es/issues/414 Improvements for proto2 required
• https://github.com/bufbuild/protobuf-es/issues/738 type-save full enum value names
• https://github.com/bufbuild/protobuf-es/issues/928 Better interop with 3rd party frameworks requiring plain objects
• https://github.com/bufbuild/protobuf-es/issues/508 JSON types

[!TIP]

Take a look at the upgrade guide to learn more.

[!NOTE]

Connect-ES does not support version 2 yet. We will update it shortly.

Contributors

Thanks to @​srikrsna-buf for his contributions to v2!

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 26a9da7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

💥 An error occurred when fetching the changed packages and changesets in this PR

Some errors occurred when validating the changesets config:
The package or glob expression "github.com/livekit/protocol" specified in the `fixed` option does not match any package in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 2.x releases. But if you manually upgrade to 2.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.