Update scale-value requirement from 0.6.0 to 0.7.0

[dependabot]

Updates the requirements on scale-value to permit the latest version.

Release notes

Sourced from scale-value's releases.

v0.7.0

0.7.0

The main change in this release is that it makes use of a new scale-encode crate and updated scale-decode crate for the SCALE encoding and decoding of Values.

• Values now implement DecodeAsType and EncodeAsType.
• Composites now implement DecodeAsFields.
• As a small breaking API change, the TypeId passed to the encode and decode methods is now a plain u32 for simplicity, rather than a newtype struct.

It should be very straightforward to update to this release as the changes are mainly additive in nature.

Changed

• Use latest scale-decode and new scale-encode crate for SCALE encoding and decoding Values. (#25)

Changelog

Sourced from scale-value's changelog.

0.7.0

The main change in this release is that it makes use of a new scale-encode crate and updated scale-decode crate for the SCALE encoding and decoding of Values.

• Values now implement DecodeAsType and EncodeAsType.
• Composites now implement DecodeAsFields.
• As a small breaking API change, the TypeId passed to the encode and decode methods is now a plain u32 for simplicity, rather than a newtype struct.

It should be very straightforward to update to this release as the changes are mainly additive in nature.

Changed

• Use latest scale-decode and new scale-encode crate for SCALE encoding and decoding Values. (#25)

0.6.0

Here we move to scale_bits from bitvec to handle our encode/decode logic and provide a simple type to decode bits into. We also now add a WASM CI test, and will expect this crate (potentially via features in the future) to be WASM compatible.

Changed

• Use scale-bits for BitSequence decoding etc and enable WASM test. (#24)

0.5.0

The main user-facing change in this release is that the SCALE bytes for compact-encoded structs previously decoded into Composite values with the same degree of nesting (ie if the compact encoded value was nested within 2 structs, it would be decoded into a value nested inside 2 Composites). This nesting has now been removed, and the compact value is returned directly. This should have no impact on re-encoding the Value, since encoding into single-field composites will just delegrate to the inner field type as needed.

Internally, the SCALE decoding logic has mostly moved to scale-decode, simplifying the logic in this crate (and exposing a more general/lower level decoding interface via that crate).

Full list of changes:

Changed

• Use scale-decode for Value decoding. (#22)

0.4.0

The main addition in this release is the At trait (and corresponding .at() method) for indexing into Values. There are also various small breaking changes as a result of tidying up various constructors, which will hopefully in general allow you to construct Values with a little less verbosity. The uint/int constructors have been made more consistent with their siblings and have been renamed to u128 and i128.

Full list of changes:

Added

• Index into values with at, and more generic/extra accessors/constructors. (#19)

0.3.0

This release introduces a small breaking change: scale_value::scale::encode_value_as_type now takes a reference to a value rather than ownership of it, since on the happy path this shouldnt affect performance, and it would often mean cloning the entire value before passing it in, anyway.

Full list of changes:

Changed

... (truncated)

Commits

• f04c1af Prep for 0.7.0 release (#27)
• 484a6e7 bump yap to latest (#26)
• 550654a Use scale-encode and scale-decode, and enable zero-copy decoding via Visitor ...
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 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)