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

deps: update jsonrpsee to v0.22.5 #4330

Merged
merged 4 commits into from
May 2, 2024

Conversation

koushiro
Copy link
Contributor

use server-core feature instead of server feature when defining the rpc api

use `server-core` feature instead of `server` feature when defining the rpc api
@koushiro koushiro requested review from andresilva and a team as code owners April 30, 2024 03:44
@@ -16,7 +16,7 @@ workspace = true
targets = ["x86_64-unknown-linux-gnu"]

[dependencies]
jsonrpsee = { version = "0.22", features = ["client-core", "macros", "server"] }
jsonrpsee = { version = "0.22", features = ["client-core", "server-core", "macros"] }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the server-core feature fails to compile before 0.22.5, maybe you need to point the version to 0.22.5.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, for downstream users, it's neceessary

@jasl
Copy link
Contributor

jasl commented Apr 30, 2024

Cool, it should be transparency for downstream but reduce several dependencies

@skunert skunert added R0-silent Changes should not be mentioned in any release notes T0-node This PR/Issue is related to the topic “node”. labels May 2, 2024
@skunert
Copy link
Contributor

skunert commented May 2, 2024

In general LGTM, just curious why this needs 22.5? Could not find anything in the jsonrpsee changelogs that seems relevant.

@koushiro
Copy link
Contributor Author

koushiro commented May 2, 2024

In general LGTM, just curious why this needs 22.5? Could not find anything in the jsonrpsee changelogs that seems relevant.

relevant PRs:

@bkchr bkchr enabled auto-merge May 2, 2024 07:45
@bkchr bkchr added this pull request to the merge queue May 2, 2024
Merged via the queue into paritytech:master with commit 4e0b3ab May 2, 2024
144 of 147 checks passed
@koushiro koushiro deleted the update-jsonrpsee branch May 2, 2024 12:52
dcolley added a commit to metaspan/polkadot-sdk that referenced this pull request May 6, 2024
* 'master' of https://github.com/metaspan/polkadot-sdk: (65 commits)
  Introduces `TypeWithDefault<T, D: Get<T>>` (paritytech#4034)
  Publish `polkadot-sdk-frame`  crate (paritytech#4370)
  Add validate field to prdoc (paritytech#4368)
  State trie migration on asset-hub westend and collectives westend (paritytech#4185)
  Fix: dust unbonded for zero existential deposit (paritytech#4364)
  Bridge: added subcommand to relay single parachain header (paritytech#4365)
  Bridge: fix zombienet tests (paritytech#4367)
  [WIP][CI] Add more GHA jobs (paritytech#4270)
  Allow for 0 existential deposit in benchmarks for `pallet_staking`, `pallet_session`, and `pallet_balances` (paritytech#4346)
  Deprecate `NativeElseWasmExecutor` (paritytech#4329)
  More `xcm::v4` cleanup and `xcm_fee_payment_runtime_api::XcmPaymentApi` nits (paritytech#4355)
  sc-tracing: enable env-filter feature (paritytech#4357)
  deps: update jsonrpsee to v0.22.5 (paritytech#4330)
  Add PoV-reclaim enablement guide to polkadot-sdk-docs (paritytech#4244)
  cargo: Update experimental litep2p to latest version (paritytech#4344)
  Bridge: ignore client errors when calling recently added `*_free_headers_interval` methods (paritytech#4350)
  Make parachain template great again (and async backing ready) (paritytech#4295)
  [Backport] Version bumps and reorg prdocs from 1.11.0 (paritytech#4336)
  HRMP - set `DefaultChannelSizeAndCapacityWithSystem` with dynamic values according to the `ActiveConfig` (paritytech#4332)
  Statement Distribution Per Peer Rate Limit (paritytech#3444)
  ...
TarekkMA pushed a commit to moonbeam-foundation/polkadot-sdk that referenced this pull request Aug 2, 2024
use `server-core` feature instead of `server` feature when defining the
rpc api
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
R0-silent Changes should not be mentioned in any release notes T0-node This PR/Issue is related to the topic “node”.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants