rust-bitcoin-unsafe-fast/hashes/extended_tests/schemars/README.md

# Test crate for the schemars feature

Run as usual with `cargo test`.

## Minimum Supported Rust Version (MSRV)

To run the tests with the MSRV you will need to pin `serde`:

- `cargo update -p serde --precise 1.0.156`
Fix pinning (schemars and MSRV) Done as is single patch to make sure all the docs and CI are in sync and correct. We currently pin the `schemars` dependency using `<=0.8.3` as well as a the `dyn-clone` transient dependency in the manifest (`hashes` and the extended test crate). This is incorrect because it makes usage of the crate klunky (or possibly impossible) if downstream users wish to use a later version of `schemars`. Observe also that we do not have to pin `schemars`, we do however have to pin the `serde` crate if either `serde` or `schemars` features are enabled. Do so in CI and document in the readme file within hashes. Currently we have a pin remaining from the old MSRV (`syn` due to use of `matches!`). Fix pinning by: - Remove pin in manifest for `schemars` - Fix pinning for MSRV in CI and docs (this includes documenting pinning requirements for `schemars` feature because it is related to the other pin of `serde`) in both `hashes` readme and main repo readme. 2023-03-06 22:39:20 +00:00			`# Test crate for the schemars feature`

			Run as usual with `cargo test`.

			`## Minimum Supported Rust Version (MSRV)`

extended_tests: Remove stale docs We no longer need to pin `syn`; remove stale docs. 2023-04-19 23:17:10 +00:00			To run the tests with the MSRV you will need to pin `serde`:
Fix pinning (schemars and MSRV) Done as is single patch to make sure all the docs and CI are in sync and correct. We currently pin the `schemars` dependency using `<=0.8.3` as well as a the `dyn-clone` transient dependency in the manifest (`hashes` and the extended test crate). This is incorrect because it makes usage of the crate klunky (or possibly impossible) if downstream users wish to use a later version of `schemars`. Observe also that we do not have to pin `schemars`, we do however have to pin the `serde` crate if either `serde` or `schemars` features are enabled. Do so in CI and document in the readme file within hashes. Currently we have a pin remaining from the old MSRV (`syn` due to use of `matches!`). Fix pinning by: - Remove pin in manifest for `schemars` - Fix pinning for MSRV in CI and docs (this includes documenting pinning requirements for `schemars` feature because it is related to the other pin of `serde`) in both `hashes` readme and main repo readme. 2023-03-06 22:39:20 +00:00
			- `cargo update -p serde --precise 1.0.156`