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

Update min rustc version and Cargo.lock file #131

Closed
wants to merge 5 commits into from

Conversation

trkohler
Copy link
Contributor

@trkohler trkohler commented Aug 24, 2024

we've discussed that we might want to bump minimum supported rustc version to 1.70.0 and also update Cargo.lock file.

@elpiel
Copy link
Member

elpiel commented Aug 25, 2024

This is totally normal. Thanks for updating the deps. This does not change the requirements for the versions when someone wants to use nmea in their project.

  • Could you take a look at the failing job?

@elpiel
Copy link
Member

elpiel commented Aug 26, 2024

I think we should stick with at least the version in Cargo.lock

Maybe it's just time to bump the MSRV again.
I see that for 0.6 we've bumped it with 5 version from 0.5 so it's safe to say that Rust 1.70 can be the MSRV.

image

@trkohler
Copy link
Contributor Author

tested locally with 1.70.0-aarch64-apple-darwin

@trkohler trkohler marked this pull request as ready for review August 26, 2024 10:23
@trkohler trkohler changed the title When I run cargo update I have noticed that there is some diff in Cargo.lock being generated Update Cargo.lock file and min rustc version in CI runner Aug 26, 2024
@trkohler trkohler changed the title Update Cargo.lock file and min rustc version in CI runner Update min rustc version and Cargo.lock file Aug 26, 2024
@elpiel elpiel mentioned this pull request Aug 26, 2024
@trkohler
Copy link
Contributor Author

closing in favour of #133

@trkohler trkohler closed this Aug 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants