Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency @bufbuild/protobuf to v2 - autoclosed #1045

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 22, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@bufbuild/protobuf (source) ^1.2.0 -> ^2.0.0 age adoption passing confidence

Release Notes

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

v2.2.2

Compare Source

What's Changed

New Contributors

Full Changelog: bufbuild/protobuf-es@v2.2.1...v2.2.2

v2.2.1

Compare Source

What's Changed

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

v2.2.0

Compare Source

What's Changed

New Contributors

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

v2.1.0

Compare Source

What's Changed

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:

[!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 renovate bot requested a review from a team as a code owner August 22, 2024 19:01
@renovate renovate bot added the renovate label Aug 22, 2024
Copy link
Contributor Author

renovate bot commented Aug 22, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact 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 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.4.2" 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.4.0" 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.4.2" 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.4.0" 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 /tmp/renovate/cache/others/npm/_logs/2024-12-04T08_23_43_074Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-04T08_23_43_074Z-debug-0.log

@renovate renovate bot force-pushed the renovate/bufbuild-protobuf-2.x branch 4 times, most recently from 1d67608 to 61fcd96 Compare September 2, 2024 09:28
@renovate renovate bot force-pushed the renovate/bufbuild-protobuf-2.x branch 2 times, most recently from ca2085d to 6c7e387 Compare September 4, 2024 18:40
@renovate renovate bot force-pushed the renovate/bufbuild-protobuf-2.x branch 3 times, most recently from 1b90d0f to ea10845 Compare September 20, 2024 19:16
@renovate renovate bot force-pushed the renovate/bufbuild-protobuf-2.x branch 7 times, most recently from 34afea4 to 9368833 Compare October 4, 2024 03:11
@renovate renovate bot force-pushed the renovate/bufbuild-protobuf-2.x branch 11 times, most recently from a0a8a1f to 0deff8b Compare October 18, 2024 19:35
@renovate renovate bot force-pushed the renovate/bufbuild-protobuf-2.x branch 12 times, most recently from c19409a to da34885 Compare October 25, 2024 17:08
@renovate renovate bot force-pushed the renovate/bufbuild-protobuf-2.x branch 3 times, most recently from 914f399 to 07e249c Compare October 29, 2024 22:35
@renovate renovate bot force-pushed the renovate/bufbuild-protobuf-2.x branch 3 times, most recently from 7ad00d7 to 8175a58 Compare November 6, 2024 18:50
@renovate renovate bot force-pushed the renovate/bufbuild-protobuf-2.x branch 3 times, most recently from 3e6d1b3 to e9382ca Compare December 2, 2024 16:14
@renovate renovate bot force-pushed the renovate/bufbuild-protobuf-2.x branch from e9382ca to 0651a37 Compare December 3, 2024 20:34
@renovate renovate bot force-pushed the renovate/bufbuild-protobuf-2.x branch from 0651a37 to 9711571 Compare December 4, 2024 08:23
@renovate renovate bot changed the title fix(deps): update dependency @bufbuild/protobuf to v2 fix(deps): update dependency @bufbuild/protobuf to v2 - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/bufbuild-protobuf-2.x branch December 8, 2024 18:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants