pezkuwichain/pezkuwi-subxt
1
0
Fork 0
mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-06-15 19:41:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

Release v0.21.0 (#525)

Browse Source 
* Bump versions to v0.21.0

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>

* Update releasing steps

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>

* Add changelog

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>

* releasing: Add categories for changelog

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>

* Update CHANGELOG.md

Co-authored-by: Tarik Gul <47201679+TarikGul@users.noreply.github.com>

* Update CHANGELOG.md

Co-authored-by: Tarik Gul <47201679+TarikGul@users.noreply.github.com>

Co-authored-by: Tarik Gul <47201679+TarikGul@users.noreply.github.com>
This commit is contained in:
Alexandru Vasile
2022-05-02 18:54:19 +03:00
committed by GitHub
parent 5c17afbfe5
commit 6d73172560
10 changed files with 53 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+36
View File
@@ -4,6 +4,42 @@ All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [0.21.0] - 2022-05-02
This release adds static metadata validation, via comparing the statically generated API with the target node's runtime
metadata. This implies a breaking change in the subxt API, as the user receives an error when interacting with an
incompatible API at the storage, call, and constant level.
The `subxt-cli` can check the compatibility of multiple runtime nodes, either full metadata compatibility or
compatibility at the pallet level.
Users can define custom derives for specific generated types of the API via adding the `derive_for_type` configuration
to the `subxt` attribute.
The metadata documentation is propagated to the statically generated API.
Previously developers wanting to build the subxt crate needed the `substrate` binary dependency in their local
environment. This restriction is removed via moving the integration tests to a dedicated crate.
The number of dependencies is reduced for individual subxt crates.
### Fixed
- test-runtime: Add exponential backoff ([#518](https://github.com/paritytech/subxt/pull/518))
### Added
- Add custom derives for specific generated types ([#520](https://github.com/paritytech/subxt/pull/520))
- Static Metadata Validation ([#478](https://github.com/paritytech/subxt/pull/478))
- Propagate documentation to runtime API ([#511](https://github.com/paritytech/subxt/pull/511))
- Add `tidext` in real world usage ([#508](https://github.com/paritytech/subxt/pull/508))
- Add system health rpc ([#510](https://github.com/paritytech/subxt/pull/510))
### Changed
- Put integration tests behind feature flag ([#515](https://github.com/paritytech/subxt/pull/515))
- Use minimum amount of dependencies for crates ([#524](https://github.com/paritytech/subxt/pull/524))
- Export `BaseExtrinsicParams` ([#516](https://github.com/paritytech/subxt/pull/516))
- bump jsonrpsee to v0.10.1 ([#504](https://github.com/paritytech/subxt/pull/504))
## [0.20.0] - 2022-04-06
The most significant change in this release is how we create and sign extrinsics, and how we manage the
RELEASING.md
+2 -2
View File
@@ -26,7 +26,7 @@ We also assume that ongoing work done is being merged directly to the `master` b
If there are minor issues with the documentation, they can be fixed in the release branch.
4. Bump the crate version in `Cargo.toml` to whatever was decided in step 2 for `subxt-cli`, `subxt-codegen`, `subxt-examples`, `subxt-macro` ,`subxt`, `test-runtime`.
4. Bump the crate version in `Cargo.toml` to whatever was decided in step 2 for `subxt-metadata`, `subxt-cli`, `subxt-codegen`, `subxt-examples`, `subxt-macro` ,`subxt`, `test-runtime`.
5. Update `CHANGELOG.md` to reflect the difference between this release and the last. If you're unsure of
what to add, check with the Tools team. See the `CHANGELOG.md` file for details of the format it follows.
@@ -41,7 +41,7 @@ We also assume that ongoing work done is being merged directly to the `master` b
```
Ensure that the script picked the latest published release tag (e.g. if releasing `v0.17.0`, the script should
provide `[+] Latest release tag: v0.16.0` ). Then group the PRs into "Added" and "Changed" sections, and make any
provide `[+] Latest release tag: v0.16.0` ). Then group the PRs into "Fixed", "Added" and "Changed" sections, and make any
other adjustments that you feel are necessary for clarity.
6. Commit any of the above changes to the release branch and open a PR in GitHub with a base of `master`.
cli/Cargo.toml
+3 -3
View File
@@ -1,6 +1,6 @@
[package]
name = "subxt-cli"
version = "0.20.0"
version = "0.21.0"
authors = ["Parity Technologies <admin@parity.io>"]
edition = "2021"
@@ -16,9 +16,9 @@ path = "src/main.rs"
[dependencies]
# perform subxt codegen
subxt-codegen = { version = "0.20.0", path = "../codegen" }
subxt-codegen = { version = "0.21.0", path = "../codegen" }
# perform node compatibility
subxt-metadata = { version = "0.20.0", path = "../metadata" }
subxt-metadata = { version = "0.21.0", path = "../metadata" }
# information of portable registry
scale-info = "2.0.0"
# parse command line args
codegen/Cargo.toml
+2 -2
View File
@@ -1,6 +1,6 @@
[package]
name = "subxt-codegen"
version = "0.20.0"
version = "0.21.0"
authors = ["Parity Technologies <admin@parity.io>"]
edition = "2021"
@@ -20,7 +20,7 @@ proc-macro-error = "1.0.4"
quote = "1.0.8"
syn = "1.0.58"
scale-info = { version = "2.0.0", features = ["bit-vec"] }
subxt-metadata = { version = "0.20.0", path = "../metadata" }
subxt-metadata = { version = "0.21.0", path = "../metadata" }
[dev-dependencies]
bitvec = { version = "1.0.0", default-features = false, features = ["alloc"] }
examples/Cargo.toml
+1 -1
View File
@@ -1,6 +1,6 @@
[package]
name = "subxt-examples"
version = "0.20.0"
version = "0.21.0"
authors = ["Parity Technologies <admin@parity.io>"]
edition = "2021"
publish = false
integration-tests/Cargo.toml
+2 -2
View File
@@ -1,6 +1,6 @@
[package]
name = "subxt-integration"
version = "0.20.0"
version = "0.21.0"
authors = ["Parity Technologies <admin@parity.io>"]
edition = "2021"
@@ -27,7 +27,7 @@ scale-info = { version = "2.0.0", features = ["bit-vec"] }
sp-core = { version = "6.0.0", default-features = false }
sp-keyring = "6.0.0"
sp-runtime = "6.0.0"
subxt = { version = "0.20.0", path = "../subxt" }
subxt = { version = "0.21.0", path = "../subxt" }
test-runtime = { path = "../test-runtime" }
tokio = { version = "1.8", features = ["macros", "time"] }
wabt = "0.10.0"
macro/Cargo.toml
+2 -2
View File
@@ -1,6 +1,6 @@
[package]
name = "subxt-macro"
version = "0.20.0"
version = "0.21.0"
authors = ["Parity Technologies <admin@parity.io>"]
edition = "2021"
autotests = false
@@ -19,4 +19,4 @@ darling = "0.14.0"
proc-macro-error = "1.0.4"
syn = "1.0.58"
subxt-codegen = { path = "../codegen", version = "0.20.0" }
subxt-codegen = { path = "../codegen", version = "0.21.0" }
metadata/Cargo.toml
+1 -1
View File
@@ -1,6 +1,6 @@
[package]
name = "subxt-metadata"
version = "0.20.0"
version = "0.21.0"
authors = ["Parity Technologies <admin@parity.io>"]
edition = "2021"
autotests = false
subxt/Cargo.toml
+3 -3
View File
@@ -1,6 +1,6 @@
[package]
name = "subxt"
version = "0.20.0"
version = "0.21.0"
authors = ["Parity Technologies <admin@parity.io>"]
edition = "2021"
@@ -31,8 +31,8 @@ serde_json = "1.0.64"
thiserror = "1.0.24"
parking_lot = "0.12.0"
subxt-macro = { version = "0.20.0", path = "../macro" }
subxt-metadata = { version = "0.20.0", path = "../metadata" }
subxt-macro = { version = "0.21.0", path = "../macro" }
subxt-metadata = { version = "0.21.0", path = "../metadata" }
sp-core = { version = "6.0.0", default-features = false }
sp-runtime = "6.0.0"
test-runtime/Cargo.toml
+1 -1
View File
@@ -1,6 +1,6 @@
[package]
name = "test-runtime"
version = "0.20.0"
version = "0.21.0"
edition = "2021"
[dependencies]