Closed lucacasonato closed 1 year ago
cc @valenting because I seem to have lost access to the repo. Can't use "Request reviews" anymore 🙃
We haven't specified an MSRV in Cargo.toml previously. I'll add that now. Scratch that, we added it recently. Updating now.
We bumped from 1.35 to 1.45 to 1.51 to 1.56 over the last two years without issue, so I don't expect this one to be a problem either. 1.60 is over a year old, so it's probably OK at this point. For a point of reference, the very widely used log
crate has MSRV >= 1.60 now.
Patch coverage has no change and project coverage change: +0.02
:tada:
Comparison is base (
0e25146
) 82.44% compared to head (d2e79da
) 82.46%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
Yep, 1.60 is quite conservative anyway, but I wasn't comfortable approving this myself :smile:
Given the past cadence, I am now
If I'm not mistaken the MSRV mismatch is caused by the debugger_test dev-dependencies (which eventually depend on log) which are actually only tested/needed on nightly for debugger_visualizer.
If that's the case, maybe we can move the dev-dependency and tests to a subcrate, and add a special CI task for it. That way we can avoid updating the MSRV just yet and make sure and make those dependencies actually nighly only?
I think we can close this for now. @lucacasonato please reopen if you still think we should up the MSRV.
This fixes CI.