Skip to content

chore(deps): update dependency @connectrpc/connect to v2 #1336

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.

Sign up for GitHub

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

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

chore(deps): update dependency @connectrpc/connect to v2 #1336

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 4, 2025

This PR contains the following updates:

Package Change Age Confidence
@connectrpc/connect (source) ^1.4.0 -> ^2.0.0 age confidence

Release Notes

connectrpc/connect-es (@​connectrpc/connect)

v2.0.2

Compare Source

What's Changed

Full Changelog: connectrpc/connect-es@v2.0.1...v2.0.2

v2.0.1

Compare Source

What's Changed

The only noteworthy changes in this release are enhancements made to the @​connectrpc/connect-migrate package.

The migration tool now handles additional scenarios for migrating your code to Connect v2:

Transforms new to create:

- import { Foo } from "./foo_pb.js";
+ import { FooSchema } from "./foo_pb.js";
+ import { create } from "@​bufbuild/protobuf";
- const foo = new Foo();
+ const foo = create(FooSchema);

Transforms isMessage to use the schema:

import { isMessage } from "@​bufbuild/protobuf";
- import { Foo } from "./foo_pb.js";
+ import { FooSchema } from "./foo_pb.js";
- isMessage(1, Foo); 
+ isMessage(1, FooSchema);

Transforms the static fromBinary, fromJson, and fromJsonString method calls:

- import { Foo } from "./foo_pb.js";
+ import { FooSchema } from "./foo_pb.js";
+ import { fromJson } from "@​bufbuild/protobuf";
- Foo.fromJson(x, y);
+ fromJson(FooSchema, x, y);

In addition, if the message is a well-known type, the import path is updated accordingly.

For details on Connect v2, see the v2 release notes as well as the full migration guide.

New Contributors

Full Changelog: connectrpc/connect-es@v2.0.0...v2.0.1

v2.0.0

Compare Source

What's Changed
  • We're upgrading to Protobuf-ES version 2. It's the largest change in this release.
  • Connect-ES no longer needs its own code generator plugin.
  • We're adding support for Next.js 15, Fastify 5, and Express 5.
  • We're dropping support for old versions of Node.js and TypeScript. You'll need at least Node.js 18.14.1 and TypeScript 4.9.6.

The upgrade of the Protobuf runtime brings support for Editions and new APIs for Protobuf messages with support for custom options. Messages are now plain TypeScript types, which greatly improves compatibility with the ecosystem. For example, messages can be passed from a server-side component in Next.js to a client-side component without losing any data or types. To learn more about the enhancements, see the release blog post for Protobuf-ES v2.

[!TIP]
If you are already using Connect, see our migration guide to upgrade to version 2.

Full Changelog

Full Changelog: connectrpc/connect-es@v1.6.1...v2.0.0

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
Copy link
Contributor Author

renovate bot commented Jul 4, 2025

⚠️ 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 unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: @bufbuild/[email protected]
npm error node_modules/@bufbuild/protobuf
npm error   @bufbuild/protobuf@"^1.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @bufbuild/protobuf@"^2.2.0" from @connectrpc/[email protected]
npm error node_modules/@connectrpc/connect
npm error   @connectrpc/connect@"^2.0.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_51_785Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-07-04T18_01_51_785Z-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@"^1.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @bufbuild/protobuf@"^2.2.0" from @connectrpc/[email protected]
npm error node_modules/@connectrpc/connect
npm error   @connectrpc/connect@"^2.0.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_56_157Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-07-04T18_01_56_157Z-debug-0.log

@renovate renovate bot added the renovate label Jul 4, 2025
@renovate renovate bot requested review from a team as code owners July 4, 2025 18:02
@renovate renovate bot added the renovate label Jul 4, 2025
@github-actions github-actions bot requested review from beeme1mr and toddbaert July 4, 2025 18:02
@renovate renovate bot changed the title chore(deps): update dependency @connectrpc/connect to v2 fix(deps): update dependency @connectrpc/connect to v2 Jul 4, 2025
@renovate renovate bot changed the title fix(deps): update dependency @connectrpc/connect to v2 chore(deps): update dependency @connectrpc/connect to v2 Jul 4, 2025
@toddbaert toddbaert closed this Jul 4, 2025
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Jul 4, 2025

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.

@renovate renovate bot deleted the renovate/connectrpc-connect-2.x branch July 4, 2025 18:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@beeme1mr beeme1mr Awaiting requested review from beeme1mr

@toddbaert toddbaert Awaiting requested review from toddbaert

Assignees

@beeme1mr beeme1mr

@toddbaert toddbaert

Labels

renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@beeme1mr @toddbaert