Bump jsonrpsee from 0.24.8 to 0.25.1

[dependabot]

Bumps jsonrpsee from 0.24.8 to 0.25.1.

Release notes

Sourced from jsonrpsee's releases.

v0.25.1

[v0.25.1] - 2025-04-24

A small follow-up patch release that adds a Clone impl for the middleware RpcLogger which was missing and broke the Clone impl for the HttpClient.

If you are updating from v0.24, have a look at https://github.com/paritytech/jsonrpsee/releases/tag/v0.25.0 because it contains some breaking changes.

Full Changelog: paritytech/jsonrpsee@v0.25.0...v0.25.1

v0.25.0

[v0.25.0] - 2025-04-24

A new breaking release which has been in the making for a while and the biggest change is that the RpcServiceT trait has been changed to support both the client and server side:

pub trait RpcServiceT {
	/// Response type for `RpcServiceT::call`.
	type MethodResponse;
	/// Response type for `RpcServiceT::notification`.
	type NotificationResponse;
	/// Response type for `RpcServiceT::batch`.
	type BatchResponse;
/// Processes a single JSON-RPC call, which may be a subscription or regular call.
fn call<'a>(&self, request: Request<'a>) -> impl Future<Output = Self::MethodResponse> + Send + 'a;
/// Processes multiple JSON-RPC calls at once, similar to RpcServiceT::call.
///
/// This method wraps RpcServiceT::call and RpcServiceT::notification,
/// but the root RPC service does not inherently recognize custom implementations
/// of these methods.
///
/// As a result, if you have custom logic for individual calls or notifications,
/// you must duplicate that implementation in this method or no middleware will be applied
/// for calls inside the batch.
fn batch<'a>(&self, requests: Batch<'a>) -> impl Future<Output = Self::BatchResponse> + Send + 'a;
/// Similar to RpcServiceT::call but processes a JSON-RPC notification.
fn notification<'a>(&self, n: Notification<'a>) -> impl Future<Output = Self::NotificationResponse> + Send + 'a;

}

The reason for this change is to make it work for the client-side as well as make it easier to implement performantly by relying on impl Future instead of requiring an associated type for the Future (which in many cases requires boxing).

The downside of this change is that one has to duplicate the logic in the batch and call method to achieve the same functionality as before. Thus, call or notification is not being invoked in the batch method and one has to implement them separately.

... (truncated)

Changelog

Sourced from jsonrpsee's changelog.

[v0.25.1] - 2025-04-24

A small follow-up patch release that adds a Clone impl for the middleware RpcLogger which was missing and broke the Clone impl for the HttpClient.

[v0.25.0] - 2025-04-24

A new breaking release which has been in the making for a while and the biggest change is that the RpcServiceT trait has been changed to support both the client and server side:

pub trait RpcServiceT {
	/// Response type for `RpcServiceT::call`.
	type MethodResponse;
	/// Response type for `RpcServiceT::notification`.
	type NotificationResponse;
	/// Response type for `RpcServiceT::batch`.
	type BatchResponse;
/// Processes a single JSON-RPC call, which may be a subscription or regular call.
fn call<'a>(&self, request: Request<'a>) -> impl Future<Output = Self::MethodResponse> + Send + 'a;
/// Processes multiple JSON-RPC calls at once, similar to RpcServiceT::call.
///
/// This method wraps RpcServiceT::call and RpcServiceT::notification,
/// but the root RPC service does not inherently recognize custom implementations
/// of these methods.
///
/// As a result, if you have custom logic for individual calls or notifications,
/// you must duplicate that implementation in this method or no middleware will be applied
/// for calls inside the batch.
fn batch<'a>(&self, requests: Batch<'a>) -> impl Future<Output = Self::BatchResponse> + Send + 'a;
/// Similar to RpcServiceT::call but processes a JSON-RPC notification.
fn notification<'a>(&self, n: Notification<'a>) -> impl Future<Output = Self::NotificationResponse> + Send + 'a;

}

The reason for this change is to make it work for the client-side as well as make it easier to implement performantly by relying on impl Future instead of requiring an associated type for the Future (which in many cases requires boxing).

The downside of this change is that one has to duplicate the logic in the batch and call method to achieve the same functionality as before. Thus, call or notification is not being invoked in the batch method and one has to implement them separately. For example now it's possible to write middleware that counts the number of method calls as follows (both client and server):

#[derive(Clone)]
pub struct Counter<S> {
	service: S,
</tr></table> 

... (truncated)

Commits

• 6540970 chore: release v0.25.1 (#1569)
• a1e95db middleware: impl Clone for RpcLogger (#1568)
• 86763a9 chore: release v0.25 (#1566)
• de59642 benchmarks: update rust 1.85.0 (#1567)
• a9a8f6d middleware: RpcServiceT distinct return types for notif, batch, call (#1564)
• 1b0799c ci: update rust version 1.84 for benchmarks (#1548)
• 0b1cb02 fix: version parsing in scripts/publish.sh (#1556)
• 90c2cc5 middleware: fix option_layer (#1562)
• 69f7fcb remove needless trait bounds (#1559)
• a2e503b fix(client): add correct default type and logger (#1558)
• 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)

[ameba23]

@dependabot rebase

[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.