paritytech / paritytech/parity-scale-codec
Backwards incompatible change in patch version
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 287
- Forks
- 103
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 1
Description
Updating from v3.6.4 -> v3.6.8 introduced a backwards incompatible change caught by ruint ci here.
Change was in this commit. Introduced in #512
Please consider yanking 3.6.7 & 3.6.8
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked ruint CI failure, then compare the change in commit 1e3f80c1e047ec67f79f12e6a8067692edb14e9d and issue #512. Determine whether v3.6.7 and v3.6.8 introduced the reported backwards incompatibility; done means documenting the finding and deciding whether those releases should be yanked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100