Bump device-driver to 1.0.9#25
Conversation
There was a problem hiding this comment.
Pull request overview
Bumps the Rust device-driver dependency to 1.0.9, updating both the manifest and lockfile to ensure builds resolve the intended crate version.
Changes:
- Updated
Cargo.tomlto requiredevice-driver1.0.9(withdefault-features = falseunchanged). - Refreshed
Cargo.lockto reflectdevice-driver1.0.9and its new checksum.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| Cargo.toml | Bumps the device-driver dependency requirement to 1.0.9. |
| Cargo.lock | Updates the resolved device-driver package entry to 1.0.9 (version + checksum). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
4a7a705 to
46372bf
Compare
46372bf to
f5a70ca
Compare
|
This one is odd. If I just generate the file |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 3 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
I'm assuming we want both format and device-driver-pregen passing. Updating CI accordingly. |
Updates the `device-driver` dependency from 1.0.3 to 1.0.9 and refreshes Cargo.lock (resolved 1.0.7 -> 1.0.9 transitively). No cargo-vet config present in this repo, so no audit certification is needed. Assisted-by: Claude:claude-opus-4.7
f5a70ca to
2b9dbb1
Compare
Bumps
device-driverfrom 1.0.3 to 1.0.9.Cargo.tomldependency declaration.Cargo.lockviacargo build.src/device.rswith nightly rustfmt to satisfy thenightly / fmtcheck (the file was previously committed in rawdevice-driver-clioutput, which doesn't match the unstablerustfmt.tomloptions used by the nightly fmt job)..github/workflows/device-driver.yml: thedevice-driver-pregen-checkjob previously diffed rawdevice-driver-clioutput against the committed file. Once the committed file is nightly-formatted, that comparison is structurally guaranteed to break (and vice versa). The workflow now installs nightly withrustfmtand runsrustup run nightly rustfmt --edition 2024 ci_gen_device.rsbetween the generate and diff steps, so the comparison happens on equivalently-formatted code.cargo clippy -- -F clippy::suspicious -F clippy::correctness -F clippy::perf -F clippy::style,cargo build,cargo test, and the new CI flow simulated end-to-end (regen → nightly rustfmt → byte-identical diff).