chore(deps): bump jsonrpsee from 0.22.5 to 0.23.2

[dependabot]

Bumps jsonrpsee from 0.22.5 to 0.23.2.

Release notes

Sourced from jsonrpsee's releases.

v0.23.2

[v0.23.2] - 2024-06-26

This a small patch release that fixes a couple of bugs and adds a couple of new APIs.

The bug fixes are:

• The server::ws::on_connect was not working properly due to a merge nit when upgrading to hyper v1.0 This impacts only users that are using the low-level API and not the server itself.
• WsTransport::build_with_stream shouldn't not resolve the socket addresses and it's fixed now, [see #1411 for further info](paritytech/jsonrpsee#1411). This impacts users that are injecting their own TcpStream directly into the WsTransport.

[Added]

• server: add RpcModule::remove (#1416)
• server: add capacity and max_capacity to the subscription API (#1414)
• server: add PendingSubscriptionSink::method_name (#1413)

[Fixed]

• server: make ws::on_connect work again (#1418)
• client: WsTransport::build_with_stream don't resolve sockaddrs (#1412)

Full Changelog: paritytech/jsonrpsee@v0.23.1...v0.23.2

v0.23.1

[v0.23.1] - 2024-06-10

This is a patch release that injects the ConnectionId in the extensions when using a RpcModule without a server. This impacts users that are using RpcModule directly (e.g., unit testing) and not the server itself.

[Changed]

• types: remove anyhow dependency (#1398)

[Fixed]

• rpc module: inject ConnectionId in extensions (#1399)

Full Changelog: paritytech/jsonrpsee@v0.23.0...v0.23.1

v0.23.0

[v0.23.0] - 2024-06-07

This is a new breaking release, and let's go through the changes.

hyper v1.0

jsonrpsee has been upgraded to use hyper v1.0 and this mainly impacts users that are using the low-level API and rely on the hyper::service::make_service_fn which has been removed, and from now on you need to manage the socket yourself.

The hyper::service::make_service_fn can be replaced by the following example template:

... (truncated)

Changelog

Sourced from jsonrpsee's changelog.

[v0.23.2] - 2024-06-26

This a small patch release that fixes a couple of bugs and adds a couple of new APIs.

The bug fixes are:

• The server::ws::on_connect was not working properly due to a merge nit when upgrading to hyper v1.0 This impacts only users that are using the low-level API and not the server itself.
• WsTransport::build_with_stream shouldn't not resolve the socket addresses and it's fixed now, [see #1411 for further info](paritytech/jsonrpsee#1411). This impacts users that are inject their own TcpStream directly into the WsTransport.

[Added]

• server: add RpcModule::remove (#1416)
• server: add capacity and max_capacity to the subscription API (#1414)
• server: add PendingSubscriptionSink::method_name (#1413)

[Fixed]

• server: make ws::on_connect work again (#1418)
• client: WsTransport::build_with_stream don't resolve sockaddrs (#1412)

[v0.23.1] - 2024-06-10

This is a patch release that injects the ConnectionId in the extensions when using a RpcModule without a server. This impacts users that are using RpcModule directly (e.g., unit testing) and not the server itself.

[Changed]

• types: remove anyhow dependency (#1398)

[Fixed]

• rpc module: inject ConnectionId in extensions (#1399)

[v0.23.0] - 2024-06-07

This is a new breaking release, and let's go through the changes.

hyper v1.0

jsonrpsee has been upgraded to use hyper v1.0 and this mainly impacts users that are using the low-level API and rely on the hyper::service::make_service_fn which has been removed, and from now on you need to manage the socket yourself.

The hyper::service::make_service_fn can be replaced by the following example template:

async fn start_server() {
  let listener = tokio::net::TcpListener::bind("127.0.0.1:0").await.unwrap();
loop {
let sock = tokio::select! {
</tr></table>

... (truncated)

Commits

• c6344f9 chore: release v0.23.2
• b7d601f add RpcModule::remove (#1416)
• 2e71ce8 fix: remove sockaddrs field from Target (#1412)
• f1475e0 fix(server): make ws::on_connect work again (#1418)
• 5279f62 feat: add capacity and max_capacity to the subscription API (#1414)
• 9de9317 feat: add PendingSubscriptionSink::method_name (#1413)
• 717e9fe chore: release 0.23.1 (#1400)
• 207dd63 fix(rpc module): inject ConnectionId in extensions (#1399)
• 5a6cb04 chore: remove anyhow dependency in types (#1398)
• 251c549 chore: release v0.23 (#1396)
• Additional commits viewable in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[niklasad1]

Requires a new subxt release

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.