We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
rev
This should be done to ensure older versions of this library still works.
See polkascan/py-subwasm-bindings#1 for motivation for example
The text was updated successfully, but these errors were encountered:
Hi @niklasad1, I am a little confused by your statement:
The problem is that subwasm is using latest master for jsonrpsee and v0.6.0 relied on old version that had many breaking changes.
as subwasm uses:
subwasm
jsonrpsee = {version = "0.4", git = "https://github.com/paritytech/jsonrpsee", features = ["full"]}
and its cargo.lock has jsonrpsee pinned to:
version = "0.4.1" source = "git+https://github.com/paritytech/jsonrpsee#ff3337b107bf29bef6067164c20c6a0b0b5bdc75"
The dependency on jsonrpsee master was likely true in the past though.
So it sounds like py-subwasm should upgrade its deps but do you see anything to be done the suwbasm side ?
py-subwasm
suwbasm
Sorry, something went wrong.
Ah, I think I got confused by that you use both git and version in Cargo.toml
git and version
nvm
No branches or pull requests
This should be done to ensure older versions of this library still works.
See polkascan/py-subwasm-bindings#1 for motivation for example
The text was updated successfully, but these errors were encountered: