-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Rust: Build from git branches #18151
Rust: Build from git branches #18151
Conversation
This makes it easier for all maintainers to adjust to C-nonbreaking but Rust-breaking API changes, as regular `cargo update` steps don't require a crates.io release any more.
This is not so much an update (riot-wrappers stays at the same commit, riot-sys just advances by one that re-enables an optional dependency, but of course third party crates are updated) but more reflects the switch from using released crates to git versions.
The referenced branches now have CI set up. I'll have to do a round of checks as to whether developer documentation needs updating (there's some in tests/rust_minimal/README.md), but from the technical aspects I think this is ready for review. |
So, these are not pinned? That means one RIOT CI commit build does not consistently point to the same code? I think I'd prefer pinning to specific commits. edit or are the exact versions pinned through Cargo.lock? |
They're pinned through the Cargo.lock files, as they were before. [edit: read post on mail, missed your edit ;-) ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK.
Contribution description
With Rust crate repositories currently being created in the RIOT group, this uses the repositories, allowing maintainers (with the usual ACKs) to fix breakage without the need to go through a crates.io release.
This enacts a switch discussed in a recent maintainers meeting.
Testing procedure