chore(deps): update dependency @bufbuild/protobuf to v2 #1335

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 "@&#8203;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 is behind base branch, 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.

renovate · 2025-07-04T18:01:48Z

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @connectrpc/[email protected]
npm error Found: @bufbuild/[email protected]
npm error node_modules/@bufbuild/protobuf
npm error   @bufbuild/protobuf@"^2.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @bufbuild/protobuf@"^1.10.0" from @connectrpc/[email protected]
npm error node_modules/@connectrpc/connect
npm error   @connectrpc/connect@"^1.4.0" from the root project
npm error   peer @connectrpc/connect@"1.6.1" from @connectrpc/[email protected]
npm error   node_modules/@connectrpc/connect-web
npm error     @connectrpc/connect-web@"^1.4.0" from the root project
npm error
npm error Conflicting peer dependency: @bufbuild/[email protected]
npm error node_modules/@bufbuild/protobuf
npm error   peer @bufbuild/protobuf@"^1.10.0" from @connectrpc/[email protected]
npm error   node_modules/@connectrpc/connect
npm error     @connectrpc/connect@"^1.4.0" from the root project
npm error     peer @connectrpc/connect@"1.6.1" from @connectrpc/[email protected]
npm error     node_modules/@connectrpc/connect-web
npm error       @connectrpc/connect-web@"^1.4.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-07-04T18_01_26_761Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-07-04T18_01_26_761Z-debug-0.log

File name: libs/providers/flagd-web/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @openfeature/[email protected]
npm error Found: @bufbuild/[email protected]
npm error node_modules/@bufbuild/protobuf
npm error   @bufbuild/protobuf@"^2.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @bufbuild/protobuf@"^1.10.0" from @connectrpc/[email protected]
npm error node_modules/@connectrpc/connect
npm error   @connectrpc/connect@"^1.4.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-07-04T18_01_40_316Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-07-04T18_01_40_316Z-debug-0.log

renovate · 2025-07-04T18:11:50Z

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.

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

6132f1b

renovate bot added the renovate label Jul 4, 2025

renovate bot requested review from a team as code owners July 4, 2025 18:01

github-actions bot assigned beeme1mr and toddbaert Jul 4, 2025

github-actions bot requested review from beeme1mr and toddbaert July 4, 2025 18:01

renovate bot changed the title ~~chore(deps): update dependency @bufbuild/protobuf to v2~~ fix(deps): update dependency @bufbuild/protobuf to v2 Jul 4, 2025

renovate bot changed the title ~~fix(deps): update dependency @bufbuild/protobuf to v2~~ chore(deps): update dependency @bufbuild/protobuf to v2 Jul 4, 2025

toddbaert closed this Jul 4, 2025

renovate bot deleted the renovate/bufbuild-protobuf-2.x branch July 4, 2025 18:11

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(deps): update dependency @bufbuild/protobuf to v2 #1335

chore(deps): update dependency @bufbuild/protobuf to v2 #1335

Uh oh!

renovate bot commented Jul 4, 2025

Uh oh!

renovate bot commented Jul 4, 2025

Uh oh!

renovate bot commented Jul 4, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

chore(deps): update dependency @bufbuild/protobuf to v2 #1335

chore(deps): update dependency @bufbuild/protobuf to v2 #1335

Uh oh!

Conversation

renovate bot commented Jul 4, 2025

Release Notes

What's Changed

What's Changed

What's Changed

What's Changed

What's Changed

What's Changed

What's Changed

What's Changed

New Contributors

What's Changed

What's Changed

New Contributors

What's Changed

What's Changed

New Contributors

What's Changed

What's new in version 2

Contributors

Configuration

Uh oh!

renovate bot commented Jul 4, 2025

⚠️ Artifact update problem

File name: package-lock.json

File name: libs/providers/flagd-web/package-lock.json

Uh oh!

renovate bot commented Jul 4, 2025

Renovate Ignore Notification

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants