tracking issue for v2 migration testing
Open
@bolshoytoster is already working on this.
Since Sep 19, 2026.
experiment
good first issue
help wanted
r-testing
- Dominant language
- Rust
- Stars
- 1.7k
- Forks
- 216
- Avg merge
- 17h 50m
- Merged PRs (30d)
- 95
Description
this is the tracking issue for testing v2 migrations
goal: take the following crates, fork them, and migrate them to v2 to see if everything works fine, including testing and benchmarking them. no need to open a PR for them, just to see if migration would be unfold and if anything would break or become significantly slower
I've chosen crates which seem to be fairly up-to-date with smallvec, it is not a perfectly curated list.
-
gix-object -
glib -
cranelift-codegen -
wasmtime -
egui -
spdx -
spade -
rpds -
ort -
libp2p-dns
the sole objective is go through migration and file issues for any conflicts or problems
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.
Assessment
This issue has not been assessed yet.