Commit f10f18d
committed
Use
The verification being done here is exactly what `--locked` is for.
Allowing the check to proceed even if it changes the dependencies
could have the benefit of showing more information. But it is not
obvious that the information it shows would be relevant to the
situation being investigated.
(If that information would usually be relevant, then
`cargo +nightly update -Zminimal-versions` may be too strong, and
`cargo +nightly update -Zdirect-minimal-versions` could be
considered. Even better than either of those *might* be, somehow,
to temporarily downgrade locked dependencies only as much as
necessary to make them all MSRV-compatible.)
In any case, `--locked` is more readable, and considerably simpler.
In addition to making complementary changes to the `msrv.yml`
workflow and to the `justfile` recipe it uses, this also changes
the `Makefile` rule corresponding to the `justfile` recipe, so they
continue to do the same thing if used in local experiments.--locked instead of checking Cargo.lock afterwards1 parent 4af6ef9 commit f10f18d
3 files changed
+4
-7
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
48 | 48 | | |
49 | 49 | | |
50 | 50 | | |
51 | | - | |
52 | 51 | | |
53 | 52 | | |
54 | | - | |
55 | | - | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
126 | 126 | | |
127 | 127 | | |
128 | 128 | | |
129 | | - | |
130 | | - | |
| 129 | + | |
| 130 | + | |
131 | 131 | | |
132 | 132 | | |
133 | 133 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
246 | 246 | | |
247 | 247 | | |
248 | 248 | | |
249 | | - | |
250 | | - | |
| 249 | + | |
| 250 | + | |
251 | 251 | | |
252 | 252 | | |
253 | 253 | | |
| |||
0 commit comments