Skip to content
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

[Bug]: MSRV with latest [email protected] is now on 1.70 #101

Closed
2 tasks done
elpiel opened this issue Feb 13, 2024 · 3 comments
Closed
2 tasks done

[Bug]: MSRV with latest [email protected] is now on 1.70 #101

elpiel opened this issue Feb 13, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@elpiel
Copy link

elpiel commented Feb 13, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Code of Conduct

  • I agree to follow this project's Code of Conduct

Current Behaviour

Although MSRV is set for -ll because of the upgrade of [email protected] MSRV is now 1.70
``

Expected Behaviour

MSRV 1.58 should be respected even with optional dependency half

Environment Information

https://github.com/AeroRust/nmea/actions/runs/7723182617/job/21052735785?pr=118

Steps To Reproduce

No response

@elpiel elpiel added the bug Something isn't working label Feb 13, 2024
@rjzak
Copy link
Member

rjzak commented Feb 15, 2024

We're using half v2.2, which is has a MSRV of 1.58. https://github.com/starkat99/half-rs/tree/08a03fd47b9241024e68bf375f2a7a84287bf481.

Maybe you're asking for half to be bumped, along with the MSRV?

Looking at your Cargo.toml, it seems your project is pulling in half 2.3, which is odd since our Cargo.toml specified 2.2. So maybe we need =2.2 to prevent the compiler from picking a newer version. But just updating dependencies is probably better :)

@elpiel
Copy link
Author

elpiel commented Feb 15, 2024

Yes, what specifying "2.2" means is "^2.2" which means that minor versions are upgraded (i.e. to 2.3).
As for my Cargo.toml, I don't actually depend on ciborium but criterion and I had to split the criterion benchmark to separate crate to avoid bumping MSRV every time a dependency of criterion bumps it.

@rjzak
Copy link
Member

rjzak commented Feb 17, 2024

Closed via #103

@rjzak rjzak closed this as completed Feb 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants