Why is qsv stuck on v16.1.0 on crates.io? #4452
jqnatividad
started this conversation in
FAQ
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
qsv uses a lot of git dependencies. In addition, qsv tracks Polars aggressively and is often ahead of its official Rust releases.
This is all in its effort to increase both performance and security, and to ensure we use the latest Polars features that are otherwise available in Polars official Python releases - which has a far faster release tempo.
Oftentimes, we even PRs to crates - but it sometimes takes a while before they're merged.
Unfortunately, this often prevents
cargo publishfrom working - that's why qsv is stuck at v16.1.0 on crates.io.See https://users.rust-lang.org/t/help-cargo-package-with-github-dependencies/96275
#2695
All reactions