renovate[bot]
commented
1 month ago ⚠️ 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: packages/trustix-nix-r13y-web/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @connectrpc/protoc-gen-connect-es@1.1.3
npm error Found: @bufbuild/protoc-gen-es@2.0.0
npm error node_modules/@bufbuild/protoc-gen-es
npm error dev @bufbuild/protoc-gen-es@"^2.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional @bufbuild/protoc-gen-es@"^1.3.3" from @connectrpc/protoc-gen-connect-es@1.1.3
npm error node_modules/@connectrpc/protoc-gen-connect-es
npm error dev @connectrpc/protoc-gen-connect-es@"^1.1.2" from the root project
npm error
npm error Conflicting peer dependency: @bufbuild/protoc-gen-es@1.10.0
npm error node_modules/@bufbuild/protoc-gen-es
npm error peerOptional @bufbuild/protoc-gen-es@"^1.3.3" from @connectrpc/protoc-gen-connect-es@1.1.3
npm error node_modules/@connectrpc/protoc-gen-connect-es
npm error dev @connectrpc/protoc-gen-connect-es@"^1.1.2" 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-07-31T05_41_38_133Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-07-31T05_41_38_133Z-debug-0.log
This PR contains the following updates:
^1.4.1->^2.0.0Release Notes
bufbuild/protobuf-es (@bufbuild/protoc-gen-es)
### [`v2.0.0`](https://togithub.com/bufbuild/protobuf-es/releases/tag/v2.0.0) [Compare Source](https://togithub.com/bufbuild/protobuf-es/compare/v1.10.0...v2.0.0) ##### What's new in version 2 To support [Protobuf editions](https://protobuf.dev/editions/overview/), 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: ```typescript 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](https://togithub.com/bufbuild/protobuf-es/blob/main/MANUAL.md#field-presence-and-default-values). This approach solves several outstanding issues, such as: - [https://github.com/bufbuild/protobuf-es/issues/397](https://togithub.com/bufbuild/protobuf-es/issues/397) Provide custom options at runtime - [https://github.com/bufbuild/protobuf-es/issues/551](https://togithub.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](https://togithub.com/bufbuild/protobuf-es/issues/414) Improvements for proto2 required - [https://github.com/bufbuild/protobuf-es/issues/738](https://togithub.com/bufbuild/protobuf-es/issues/738) type-save full enum value names - [https://github.com/bufbuild/protobuf-es/issues/928](https://togithub.com/bufbuild/protobuf-es/issues/928) Better interop with 3rd party frameworks requiring plain objects - [https://github.com/bufbuild/protobuf-es/issues/508](https://togithub.com/bufbuild/protobuf-es/issues/508) JSON types > \[!TIP] > > Take a look at the [upgrade guide](https://togithub.com/bufbuild/protobuf-es/blob/main/MANUAL.md#migrating-from-version-1) to learn more. > \[!NOTE] > > [Connect-ES](https://togithub.com/connectrpc/connect-es) does not support version 2 yet. We will update it shortly. ##### Contributors Thanks to [@srikrsna-buf](https://togithub.com/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.
This PR was generated by Mend Renovate. View the repository job log.