Closed frol closed 10 months ago
Since the breaking change is under unstable__schema
feature, it should not be 2.0 release, so we will need to update this release manually before merging this PR.
Since the breaking change is under
unstable__schema
feature, it should not be 2.0 release, so we will need to update this release manually before merging this PR.
there was no breaking change, this was due to exclamation mark chore!
pop!ping up in master commit message somewhat unexpectedly.
🤖 New release
borsh
: 1.1.0 -> 1.1.1 (✓ API compatible changes)borsh-derive
: 1.1.0 -> 1.1.1Changelog
## `borsh`
This PR was generated with release-plz.