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.

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

Bump jsonrpsee from 0.16.3 to 0.22.2 #13

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 7, 2024

Bumps jsonrpsee from 0.16.3 to 0.22.2.

Release notes

Sourced from jsonrpsee's releases.

v0.22.2

[v0.22.2] - 2024-03-05

This is a small patch release that exposes the connection details to server methods without breaking changes. Currently, users can only retrieve the connection ID from these details. We plan to extend this functionality in jsonrpsee v1.0, although this will necessitate a breaking change.

[Added]

  • server: Register raw method with connection ID (#1297)

[Changed]

  • Update Syn 1.0 -> 2.0 (#1304)

v0.22.1

[v0.22.1] - 2024-02-19

This is a small patch release that internally changes AtomicU64 to AtomicUsize to support more targets.

[Fixed]

  • fix(docs): part of proc-macro documentation not rendering correctly in IDE (#1294)
  • fix(client): change to AtomicU64 to AtomicUsize (#1293)
  • fix(server): low-level API return err on WS handshake err (#1288)

v0.22.0

[v0.22.0] - 2024-02-07

Another breaking release where a new ResponsePayload type is introduced in order to make it possible to determine whether a response has been processed.

Unfortunately, the IntoResponse trait was modified to enable that and some minor changes were made to make more fields private to avoid further breakage.

Example of the async ResponsePayload API

#[rpc(server)]
pub trait Api {
	#[method(name = "x")]
	fn x(&self) -> ResponsePayload<'static, String>;
}
impl RpcServer for () {
fn x(&self) -> ResponsePayload<'static, String> {
let (rp, rp_done) = ResponsePayload::success("ehheeheh".to_string()).notify_on_completion();
	tokio::spawn(async move {
		if rp_done.await.is_ok() {
			do_task_that_depend_x();

</tr></table>

... (truncated)

Changelog

Sourced from jsonrpsee's changelog.

[v0.22.2] - 2024-03-05

This is a small patch release that exposes the connection details in server method implementations without breaking changes. We plan to extend this functionality in jsonrpsee v1.0, although this will necessitate a breaking change.

[Added]

  • server: Register raw method with connection ID (#1297)

[Changed]

  • Update Syn 1.0 -> 2.0 (#1304)

[v0.22.1] - 2024-02-19

This is a small patch release that internally changes AtomicU64 to AtomicUsize to support more targets.

[Fixed]

  • fix(docs): part of proc-macro documentation not rendering correctly in IDE (#1294)
  • fix(client): change to AtomicU64 to AtomicUsize (#1293)
  • fix(server): low-level API return err on WS handshake err (#1288)

[v0.22.0] - 2024-02-07

Another breaking release where a new ResponsePayload type is introduced in order to make it possible to determine whether a response has been processed.

Unfortunately, the IntoResponse trait was modified to enable that and some minor changes were made to make more fields private to avoid further breakage.

Example of the async ResponsePayload API

#[rpc(server)]
pub trait Api {
	#[method(name = "x")]
	fn x(&self) -> ResponsePayload<'static, String>;
}
impl RpcServer for () {
fn x(&self) -> ResponsePayload<'static, String> {
let (rp, rp_done) = ResponsePayload::success("ehheeheh".to_string()).notify_on_completion();
	tokio::spawn(async move {
		if rp_done.await.is_ok() {
			do_task_that_depend_x();
		}
	});
rp


</tr></table>

... (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 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)

Bumps [jsonrpsee](https://github.com/paritytech/jsonrpsee) from 0.16.3 to 0.22.2.
- [Release notes](https://github.com/paritytech/jsonrpsee/releases)
- [Changelog](https://github.com/paritytech/jsonrpsee/blob/master/CHANGELOG.md)
- [Commits](paritytech/jsonrpsee@v0.16.3...v0.22.2)

---
updated-dependencies:
- dependency-name: jsonrpsee
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Copy link
Contributor Author

dependabot bot commented on behalf of github Mar 7, 2024

The following labels could not be found: A1-insubstantial, R0-silent.

Copy link
Contributor Author

dependabot bot commented on behalf of github Mar 28, 2024

Superseded by #16.

@dependabot dependabot bot closed this Mar 28, 2024
@dependabot dependabot bot deleted the dependabot/cargo/jsonrpsee-0.22.2 branch March 28, 2024 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants