Ralph Ursprung

see also the discussion on #410 - i think you wanted to push `hash32` to 1.0 first (https://github.com/rust-embedded-community/hash32/issues/17)?

oh, sorry, i didn't even realise that! i just looked around a bit and it seems that it'll need this nightly feature to be stabilised: https://github.com/rust-lang/rust/issues/67792 once that's done it...

this will fail to build at the moment. i've intentionally pushed it already with the new version in `Cargo.toml` so that you can just re-trigger CI once you've released `xml-rpc`...

> is this a problem because of the warning, or is this a problem because of the non-zero return code? i found it confusing since pressing Ctrl+C is the obvious...

you're right, the problem seems to be that there are no windows x64 builds attached to the release. i'm not familiar with your GH workflows, but from glancing at it...

i guess it might make sense to report this to the downstream ubuntu packaging rather than reporting it here (though this issue did help me to find the answer on...

> Did you reported it to ubuntu packaging already? no, i don't have an account there (i already collect enough accounts as it is; don't need one more just for...

as [per the docs](https://github.com/microsoft/winget-create/blob/main/doc/update.md) it shouldn't be interactive: > The update command is non-interactive [..] i think better than prompting would be to supply it an optional release notes URL...

in my understanding you don't need `shared-bus` for `embedded-hal` 1 anymore, you can use [`embedded-hal-bus`](https://github.com/rust-embedded/embedded-hal/tree/master/embedded-hal-bus) instead. `shared-bus` is only needed for `embedded-hal` 0.2.x probably there should be a `shared-bus` 0.4.0...

i don't see you using `embedded-hal-bus` in your code? but i'm no expert in this topic and haven't used freeRTOS. maybe ask in the [rust-embedded matrix room](https://matrix.to/#/#rust-embedded:matrix.org), someone there might...