Allow future `exclude-newer` values during `uv lock --check`
#19571Comparing
zb/lock-check-newer-timestamp
(3a70f5a
) withmain
(d190665
)0%
- Untouched
- 5
- Ignored
- 1
Benchmarks
6 total
resolve_warm_airflow
crates/uv-bench/benches/uv.rs::uv::resolve_warm_airflow0%
524 ms521.7 ms
resolve_warm_jupyter
crates/uv-bench/benches/uv.rs::uv::resolve_warm_jupyter0%
45.8 ms45.8 ms
resolve_warm_jupyter_universal
crates/uv-bench/benches/uv.rs::uv::resolve_warm_jupyter_universal0%
215.1 ms215.4 ms
resolve_warm_jupyter_universal
crates/uv-bench/benches/uv.rs::uv::resolve_warm_jupyter_universal-1%
144.4 ms145.7 ms
resolve_warm_jupyter
crates/uv-bench/benches/uv.rs::uv::resolve_warm_jupyter-1%
80.3 ms81.2 ms
The benchmarks below are ignored and won't be included in regression detection.
Learn more about ignoring benchmarks
Learn more about ignoring benchmarks
resolve_warm_airflow
crates/uv-bench/benches/uv.rs::uv::resolve_warm_airflowIgnored
-1%
874.3 ms880 ms
Commits
Click on a commit to change the comparison rangeBase
main
d190665
-0.38%
Allow future `exclude-newer` values during `uv lock --check`
3a70f5a
2 hours ago
by zanieb