Frequent dependency failures - substrate, polkadot, and subxt dependency mismatches
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 489
- Forks
- 293
- Avg merge
- 18h 35m
- Merged PRs (30d)
- 3
Description
We are building a CLI tool with subxt, but try to keep everything in a single workspace. This breaks frequently due to version mismatches of i.e. wasmtime and causes more friction than needed. We are not particularly keen on splitting the workspace into two.
Could it be viable to have a substrate/polkadot branch in subxt to be released in lockstep with the substrate versions that are used in polkadot?
Pretty sure this is the wrong place to file, but technically it'd need to be in all 3 repositories
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
The issue names no files, tests, or entry points. Start by reviewing dependency versions and workspace relationships across subxt, substrate, and polkadot, including the wasmtime mismatch. Done would require an agreed, actionable compatibility and release strategy across all three repositories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100