-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce and enforce MSRV #56
Comments
Pinning could break other projects, I would like to avoid it if possible. What do you think of the approach followed by Obviously, without the feature, you need to provide |
I think introducing this approach here might be a good first step, which at least would allow us to mitigate the issue by downloading the binary ourselves in CI. However, it is of course quite tedious to make our test run in CI as well as locally. As this is exactly the point of the download feature, it would be really nice to keep using it with a lower MSRV. Would an alternative path maybe be to introduce a new feature that rather than relying on |
One thing we have in rust-hwi in order to avoid pinning dependencies for everyone (as it caused some troubles: bitcoindevkit/rust-hwi#72) is a feature with a lower msrv, in which the dependencies are pinned: bitcoindevkit/rust-hwi#73 I personally don't like the approach, but it seems to work |
yeah, I think pinning via a specific feature is not great but the best option |
Sorry for the delay here. I'm experimenting with the optional dependency, not entirely sure it will work as expected, since it's a bit unclear to me how to still maintain the non-pinned default dependecy. That said, the first step towards any MSRV is probably #58, as |
@RCasatta It seems by now this crate requires ~1.67 or so just due to some downstream dependency (I think |
A dependency of
zip
recently bumped therustc
requirement to 1.6, leading to MSRV violations in downstream projects such as LDK (cf. lightningdevkit/rust-lightning#2055) and BDK:It would be great if this crate and
bitcoind
could pin an old version ofzip
and enforce a reasonable MSRV, e.g., 1.48, which would allow us to keep using them.Happy to open corresponding PRs after a concept ACK.
The text was updated successfully, but these errors were encountered: