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

Prep for 0.13.0 release #57

Merged
merged 1 commit into from
May 15, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 14 additions & 3 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,17 @@ The format is based on [Keep a Changelog].

[Keep a Changelog]: http://keepachangelog.com/en/1.0.0/

## 0.13.0 - 2023-05-15

This minor release avoids a couple of panics in the case of invalid bytes being interpreted as BitVecs or strings.

A small API change was made to accommodate this, such that the `Str::bytes_after` now returns a result rather than just the bytes.

### Fixed

- Avoid panic on invalid bitvec input bytes ([#53](https://github.com/paritytech/scale-decode/pull/53)
- Avoid panic on invalid str input bytes ([#54](https://github.com/paritytech/scale-decode/pull/54))

## 0.12.0 - 2024-04-29

Update the `scale-type-resolver` dependency to 0.2.0 (and bump `scale-bits` for the same reason).
Expand Down Expand Up @@ -174,7 +185,7 @@ Any `Visitor` impls will need to be updated to use the refined `Visitor` trait;
(check out the examples and follow the compiler guidance to do this). Otherwise, the rest of the changes are
additive and just make it easier to implement this trait and obtain a `DecodeAsType` implementation, if desired.

## Changed
### Changed

- Add DecodeAsType backed by Visitor impls for standard types. ([#11](https://github.com/paritytech/scale-decode/pull/11))

Expand All @@ -183,7 +194,7 @@ additive and just make it easier to implement this trait and obtain a `DecodeAsT
This release removes `bitvec` and the 32bit feature flag needed to play nicely with it and leans on `scale-bits` instead
to decode bit sequences. We add a CI check to ensure that it can be compiled to WASM.

## Changed
### Changed

- Use scale-bits to handle bit sequences ([#5](https://github.com/paritytech/scale-decode/pull/5)

Expand All @@ -203,7 +214,7 @@ This release makes the following changes:
- `Visitor` related types are now exported directly from the `visitor` module rather than a `visitor::types` module.
- Lifetimes have been made more precise to avoid unnecessary lifetime related errors.

## Changed
### Changed

- TypeIds, more info for compact encoded values and tidy up ([#1](https://github.com/paritytech/scale-decode/pull/1))

Expand Down
6 changes: 3 additions & 3 deletions Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ members = [
resolver = "2"

[workspace.package]
version = "0.12.0"
version = "0.13.0"
authors = ["Parity Technologies <[email protected]>"]
edition = "2021"
license = "Apache-2.0"
Expand All @@ -17,5 +17,5 @@ keywords = ["parity", "scale", "decoding"]
include = ["Cargo.toml", "src/**/*.rs", "README.md", "LICENSE"]

[workspace.dependencies]
scale-decode = { version = "0.12.0", path = "scale-decode" }
scale-decode-derive = { version = "0.12.0", path = "scale-decode-derive" }
scale-decode = { version = "0.13.0", path = "scale-decode" }
scale-decode-derive = { version = "0.13.0", path = "scale-decode-derive" }
Loading