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

Update dependency @bufbuild/protoc-gen-es to v2 - autoclosed #349

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 31, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@bufbuild/protoc-gen-es (source) ^1.7.2 -> ^2.0.0 age adoption passing confidence

Release Notes

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

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!

v1.10.0

Compare Source

What's Changed

Full Changelog: bufbuild/protobuf-es@v1.9.0...v1.10.0

v1.9.0

Compare Source

What's Changed

New Contributors

Full Changelog: bufbuild/protobuf-es@v1.8.0...v1.9.0

v1.8.0

Compare Source

What's Changed

New Contributors

Full Changelog: bufbuild/protobuf-es@v1.7.2...v1.8.0


Configuration

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

🚦 Automerge: Enabled.

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 added the dependencies Pull requests that update a dependency file label Jul 31, 2024
@renovate renovate bot enabled auto-merge (squash) July 31, 2024 03:01
Copy link
Contributor Author

renovate bot commented Jul 31, 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: frontend/pnpm-lock.yaml
octavio                                  |  WARN  Unsupported engine: wanted: {"node":"^18"} (current: {"node":"v20.17.0","pnpm":"8.15.9"})
Scope: all 4 workspace projects
/tmp/renovate/repos/github/ictsc/ictsc-regalia/frontend/packages/ui:
 ERR_PNPM_WORKSPACE_PKG_NOT_FOUND  In packages/ui: "zenn-content-css@workspace:*" is in the dependencies but no package named "zenn-content-css" is present in the workspace

This error happened while installing a direct dependency of /tmp/renovate/repos/github/ictsc/ictsc-regalia/frontend/packages/ui

Packages found in the workspace: frontend, duardo, octavio, @repo/ui

renovate-approve[bot]
renovate-approve bot previously approved these changes Jul 31, 2024
@renovate renovate bot force-pushed the renovate/bufbuild-protoc-gen-es-2.x branch 4 times, most recently from d18efc7 to 3d10602 Compare August 11, 2024 01:51
@renovate renovate bot force-pushed the renovate/bufbuild-protoc-gen-es-2.x branch from 3d10602 to 6be2b87 Compare August 22, 2024 05:45
renovate-approve[bot]
renovate-approve bot previously approved these changes Aug 22, 2024
renovate-approve[bot]
renovate-approve bot previously approved these changes Aug 22, 2024
@renovate renovate bot force-pushed the renovate/bufbuild-protoc-gen-es-2.x branch from a53fc8d to 2dd1b73 Compare August 31, 2024 12:23
@renovate renovate bot changed the title chore(deps): update dependency @bufbuild/protoc-gen-es to v2 Update dependency @bufbuild/protoc-gen-es to v2 Aug 31, 2024
Copy link
Contributor

github-actions bot commented Aug 31, 2024

The latest Buf updates on your PR. Results from workflow Proto CI Pipeline / breaking (pull_request).

BuildFormatLintBreakingUpdated (UTC)
✅ passed✅ passed✅ passed✅ passedSep 7, 2024, 11:43 AM

@renovate renovate bot force-pushed the renovate/bufbuild-protoc-gen-es-2.x branch 3 times, most recently from 55d83cb to 81394ba Compare September 6, 2024 05:31
@renovate renovate bot force-pushed the renovate/bufbuild-protoc-gen-es-2.x branch from 81394ba to f72ff37 Compare September 7, 2024 11:43
@renovate renovate bot changed the title Update dependency @bufbuild/protoc-gen-es to v2 Update dependency @bufbuild/protoc-gen-es to v2 - autoclosed Sep 9, 2024
@renovate renovate bot closed this Sep 9, 2024
auto-merge was automatically disabled September 9, 2024 16:15

Pull request was closed

@renovate renovate bot deleted the renovate/bufbuild-protoc-gen-es-2.x branch September 9, 2024 16:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants