paritytech / paritytech/host-rust-core
Release drift: published versions do not match the default branch
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 10
- Forks
- 3
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 148
Description
The default branch declares versions that do not match what is published.
@parity/truapi-debugger@0.1.4
Check the most recent Release run for a failed publish or an omitted target. Document deliberately unpublished versions in .github/registry-drift-exceptions.json with a reason.
Contributor guide
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 registry-drift workflow at .github/workflows/registry-drift.yml and inspect the most recent Release run for the reported package. Check whether the mismatch comes from a failed publish or omitted target; if the version is intentionally unpublished, record it with a reason in .github/registry-drift-exceptions.json. Done means the drift is explained and the check no longer reports an unexplained mismatch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100