search

zdave-parity / polkadot-bulletin-chain

MIT No Attribution
0 stars 3 forks source link

Bump jsonrpsee from 0.16.2 to 0.19.0 #2

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps jsonrpsee from 0.16.2 to 0.19.0.

Release notes

Sourced from jsonrpsee's releases.

V0.19.0

Fixed

  • Fixed connections processing await on server shutdown (#1153)
  • fix: include error code in RpcLogger (#1135)
  • fix: downgrade more logs to debug (#1127)
  • fix(server): remove MethodSinkPermit to fix backpressure issue on concurrent subscriptions (#1126)
  • fix readme links (#1152)

Changed

  • server: downgrade connection logs to debug (#1123)
  • refactor(server): make Server::start infallible and add fn builder() (#1137)

v0.18.2

This release improves error message for too big batch response and exposes the BatchRequestConfig type in order to make it possible to use ServerBuilder::set_batch_request_config

Fixed

  • server: export BatchRequestConfig (#1112)
  • fix(server): improve too big batch response msg (#1107)

v0.18.1

This release fixes a couple bugs and improves the ergonomics for the HTTP client when no tower middleware is enabled.

Changed

  • http client: add default generic param for the backend (#1099)

Fixed

  • rpc module: fix race in subscription close callback (#1098)
  • client: add missing batch request tracing span (#1097)
  • ws server: don't wait for graceful shutdown when connection already closed (#1103)

v0.18.0

[v0.18.0] - 2023-04-21

This is a breaking release that removes the CallError which was used to represent a JSON-RPC error object that could happen during JSON-RPC method call and one could assign application specific error code, message and data in a specific implementation.

Previously jsonrpsee provided CallError that could be converted to/from jsonrpsee::core::Error and in some scenarios the error code was automatically assigned by jsonrpsee. After jsonrpsee added support for custom error types the CallError doesn't provide any benefit because one has to implement Into<ErrorObjectOwned> on the error type anyway.

Thus, jsonrpsee::core::Error can't be used in the proc macro API anymore and the type alias RpcResult has been modified to Result<(), ErrorObjectOwned> instead.

Before it was possible to do:

... (truncated)

Changelog

Sourced from jsonrpsee's changelog.

[v0.19.0] - 2023-07-20

[Fixed]

  • Fixed connections processing await on server shutdown (#1153)
  • fix: include error code in RpcLogger (#1135)
  • fix: downgrade more logs to debug (#1127)
  • fix(server): remove MethodSinkPermit to fix backpressure issue on concurrent subscriptions (#1126)
  • fix readme links (#1152)

[Changed]

  • server: downgrade connection logs to debug (#1123)
  • refactor(server): make Server::start infallible and add fn builder() (#1137)

[v0.18.2] - 2023-05-10

This release improves error message for too big batch response and exposes the BatchRequestConfig type in order to make it possible to use ServerBuilder::set_batch_request_config

[Fixed]

  • server: export BatchRequestConfig (#1112)
  • fix(server): improve too big batch response msg (#1107)

[v0.18.1] - 2023-04-26

This release fixes a couple bugs and improves the ergonomics for the HTTP client when no tower middleware is enabled.

[Changed]

  • http client: add default generic param for the backend (#1099)

[Fixed]

  • rpc module: fix race in subscription close callback (#1098)
  • client: add missing batch request tracing span (#1097)
  • ws server: don't wait for graceful shutdown when connection already closed (#1103)

[v0.18.0] - 2023-04-21

This is a breaking release that removes the CallError which was used to represent a JSON-RPC error object that could happen during JSON-RPC method call and one could assign application specific error code, message and data in a specific implementation.

Previously jsonrpsee provided CallError that could be converted to/from jsonrpsee::core::Error and in some scenarios the error code was automatically assigned by jsonrpsee. After jsonrpsee added support for custom error types the CallError doesn't provide any benefit because one has to implement Into<ErrorObjectOwned> on the error type anyway.

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 1 year ago

Superseded by #8.