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

build(deps): bump jsonrpsee-core from 0.16.2 to 0.24.2 #1745

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Aug 5, 2024

Bumps jsonrpsee-core from 0.16.2 to 0.24.2.

Release notes

Sourced from jsonrpsee-core's releases.

v0.24.2

[v0.24.2] - 2024-08-02

Another small release that fixes:

  • Notifications without params were not handled correctly in the client, which been has been fixed.
  • Improve compile times and reduce code-generation in the proc macro crate.

[Fixed]

  • client: parse notification without params (#1436)
  • proc macros: remove direct tracing calls (#1405)

Thanks to the external contributor @​DaniPopes who contributed to this release.

Full Changelog: paritytech/jsonrpsee@v0.24.1...v0.24.2

v0.24.1

[v0.24.1] - 2024-07-30

This is a small release that forces jsonrpsee rustls to use the crypto backend ring which may panic if both ring and aws-lc features are enabled. See rustls/rustls#1877 for further information.

This has no impact on the default configuration of jsonrpsee which was already using ring as the default.

[Changed]

  • chore(deps): update gloo-net requirement from 0.5.0 to 0.6.0 (#1428)

[Fixed]

  • fix: Explicitly set rustls provider before using rustls (#1424)

Full Changelog: paritytech/jsonrpsee@v0.24.0...v0.24.1

v0.24.0

[v0.24.0] - 2024-07-05

A breaking release that mainly changes:

  1. tls feature for the client has been divided into tls and tls-platform-verifier where the tls feature will only include rustls and no specific certificate store but the default one is still tls-rustls-platform-verifier. This is useful if one wants to avoid bring on openssl dependencies.
  2. Remove dependencies anyhow and beef from the codebase.

[Changed]

  • types: serialize id in Response before result/error fields (#1421)
  • refactor(client+transport)!: split tls into tls and tls-rustls-platform-verifier features (#1419)
  • chore(deps): update rustc-hash requirement from 1 to 2 (#1410)
  • deps: remove anyhow (#1402)
  • deps: remove beef (#1401)

v0.23.2

[v0.23.2] - 2024-06-26

... (truncated)

Changelog

Sourced from jsonrpsee-core's changelog.

[v0.24.2] - 2024-08-02

Another small release that fixes:

  • Notifications without params were not handled correctly in the client, which been has been fixed.
  • Improve compile times and reduce code-generation in the proc macro crate.

[Fixed]

  • client: parse notification without params (#1436)
  • proc macros: remove direct tracing calls (#1405)

Thanks to the external contributor @​DaniPopes who contributed to this release.

[v0.24.1] - 2024-07-30

This is a small release that forces jsonrpsee rustls to use the crypto backend ring which may panic if both ring and aws-lc features are enabled. See rustls/rustls#1877 for further information.

This has no impact on the default configuration of jsonrpsee which was already using ring as the default.

[Changed]

  • chore(deps): update gloo-net requirement from 0.5.0 to 0.6.0 (#1428)

[Fixed]

  • fix: Explicitly set rustls provider before using rustls (#1424)

[v0.24.0] - 2024-07-05

A breaking release that mainly changes:

  1. tls feature for the client has been divided into tls and tls-platform-verifier where the tls feature will only include rustls and no specific certificate store but the default one is still tls-rustls-platform-verifier. This is useful if one wants to avoid bring on openssl dependencies.
  2. Remove dependencies anyhow and beef from the codebase.

[Changed]

  • types: serialize id in Response before result/error fields (#1421)
  • refactor(client+transport)!: split tls into tls and tls-rustls-platform-verifier features (#1419)
  • chore(deps): update rustc-hash requirement from 1 to 2 (#1410)
  • deps: remove anyhow (#1402)
  • deps: remove beef (#1401)

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

... (truncated)

Commits
  • c9e26b0 chore: release v0.24.2 (#1439)
  • 6c29395 fix(client): parse notification without params (#1436)
  • bc7f8eb chore: remove direct tracing calls from proc-macros (#1405)
  • 4cea488 chore(deps): update console-subscriber requirement from 0.3.0 to 0.4.0 (#1432)
  • 65fcb8c chore: release v0.24.1 (#1431)
  • f4ff5a1 chore(deps): update gloo-net requirement from 0.5.0 to 0.6.0 (#1428)
  • c70c10b fix: Explicitly set rustls provider before using rustls (#1424)
  • 7b87b64 update expected result and force recent trybuidl to avoid jsonrpsee not found...
  • fc75a88 chore: release v0.24.0 (#1422)
  • 87999cf feat(types): serialize id in Response before result/error fields (#1421)
  • Additional commits viewable in compare view

Dependabot compatibility score

You can trigger a rebase of this PR 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-core](https://github.com/paritytech/jsonrpsee) from 0.16.2 to 0.24.2.
- [Release notes](https://github.com/paritytech/jsonrpsee/releases)
- [Changelog](https://github.com/paritytech/jsonrpsee/blob/master/CHANGELOG.md)
- [Commits](paritytech/jsonrpsee@v0.16.2...v0.24.2)

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

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file rust Pull requests that update Rust code labels Aug 5, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Aug 15, 2024

Superseded by #1757.

@dependabot dependabot bot closed this Aug 15, 2024
@dependabot dependabot bot deleted the dependabot/cargo/jsonrpsee-core-0.24.2 branch August 15, 2024 11:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file rust Pull requests that update Rust code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants