kornia/kornia-rs
View on GitHub[Feature]: Add --all-features and --all-targets to CI check
Open
#736 opened on Feb 23, 2026
enhancementhelp wantedtriage
Repository metrics
- Stars
- (675 stars)
- PR merge metrics
- (PR metrics pending)
Description
Problem
Currently, our CI pipeline runs cargo check using default features only. This creates a blind spot where feature-gated code (e.g., code residing behind #[cfg(feature = "approx")]) can compile locally for a developer but break silently in other configurations, or vice versa.
We recently identified that optional dependencies are not being consistently validated, leading to potential "bit rot" in non-default crate configurations.
Proposed Solution
We should update our GitHub Actions workflow (or relevant CI config) to ensure we are testing the full surface area of our crates. Specifically, we should run:
cargo check --workspace --all-targets --all-features