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.

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

Update dependency @connectrpc/protoc-gen-connect-es to v1.5.0 #1253

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update dependency @connectrpc/protoc-gen-connect-es to v1.5.0 #1253

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 9, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@connectrpc/protoc-gen-connect-es (source) 1.1.3 -> 1.5.0 age adoption passing confidence

Release Notes

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

v1.5.0

Compare Source

v1.4.0

Compare Source

What's Changed

This release includes support for server-side interceptors! Here's a quick example:

import * as http from "http";
import routes from "./connect";
import { connectNodeAdapter } from "@​connectrpc/connect-node";
import type { Interceptor } from "@​connectrpc/connect";

const logger: Interceptor = (next) => async (req) => {
  console.log(`recevied message on ${req.url}`);
  return await next(req);
};

http
  .createServer(
    connectNodeAdapter({
      routes,
      interceptors: [logger],
    }),
  )
  .listen(8080);

For more on them please see the docs.

Other Changes
New Contributors

Full Changelog: connectrpc/connect-es@v1.3.0...v1.4.0

v1.3.0

Compare Source

What's Changed

New Contributors

Full Changelog: connectrpc/connect-es@v1.2.1...v1.3.0

v1.2.1

Compare Source

What's Changed

Full Changelog: connectrpc/connect-es@v1.2.0...v1.2.1

v1.2.0

Compare Source

What's Changed

By default, protoc-gen-connect-es (and all other plugins based on @​bufbuild/protoplugin) generate ECMAScript import and export statements. For use cases where CommonJS is difficult to avoid, a new plugin option has been added named js_import_style which can be used to generate CommonJS require() calls.

Here is an example buf.gen.yaml:

version: v1
plugins:

### You'll need @​bufbuild/protoc-gen-es v1.6.0 or later
  - plugin: es
    out: src/gen
    opt: js_import_style=legacy_commonjs
  - plugin: connect-es
    out: src/gen
    opt: js_import_style=legacy_commonjs

To view the full PR, see Support CommonJS in protoc-gen-connect-es by @​timostamm in #​956

Full Changelog: connectrpc/connect-es@v1.1.4...v1.2.0

v1.1.4

Compare Source

What's Changed

Full Changelog: connectrpc/connect-es@v1.1.3...v1.1.4

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 Apr 9, 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @otomadb/[email protected]
npm ERR! Found: @connectrpc/[email protected]
npm ERR! node_modules/@connectrpc/connect
npm ERR!   @connectrpc/connect@"^1.1.3" from the root project
npm ERR!   peer @connectrpc/connect@"1.1.3" from @connectrpc/[email protected]
npm ERR!   node_modules/@connectrpc/connect-node
npm ERR!     @connectrpc/connect-node@"^1.1.3" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! dev @connectrpc/protoc-gen-connect-es@"1.4.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @connectrpc/[email protected]
npm ERR! node_modules/@connectrpc/connect
npm ERR!   peerOptional @connectrpc/connect@"1.4.0" from @connectrpc/[email protected]
npm ERR!   node_modules/@connectrpc/protoc-gen-connect-es
npm ERR!     dev @connectrpc/protoc-gen-connect-es@"1.4.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-04-09T19_15_55_401Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-09T19_15_55_401Z-debug-0.log

@renovate renovate bot force-pushed the renovate/connectrpc-protoc-gen-connect-es-1.x branch from 965dce6 to 82ee9fb Compare September 11, 2024 13:45
@renovate renovate bot changed the title Update dependency @connectrpc/protoc-gen-connect-es to v1.4.0 Update dependency @connectrpc/protoc-gen-connect-es to v1.5.0 Sep 11, 2024
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Sep 11, 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: @otomadb/[email protected]
npm error Found: @connectrpc/[email protected]
npm error node_modules/@connectrpc/connect
npm error   @connectrpc/connect@"^1.1.3" from the root project
npm error   peer @connectrpc/connect@"1.1.3" from @connectrpc/[email protected]
npm error   node_modules/@connectrpc/connect-node
npm error     @connectrpc/connect-node@"^1.1.3" from the root project
npm error
npm error Could not resolve dependency:
npm error dev @connectrpc/protoc-gen-connect-es@"1.5.0" from the root project
npm error
npm error Conflicting peer dependency: @connectrpc/[email protected]
npm error node_modules/@connectrpc/connect
npm error   peerOptional @connectrpc/connect@"1.5.0" from @connectrpc/[email protected]
npm error   node_modules/@connectrpc/protoc-gen-connect-es
npm error     dev @connectrpc/protoc-gen-connect-es@"1.5.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-09-11T13_44_55_680Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-09-11T13_44_55_680Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants