Skip to content

Cut new tag for embassy-sync and embassy-rp please? #5212

@FransUrbo

Description

@FransUrbo

Sorry, even I can see that this is a bit .. rude, I'm sure you're all busy, but I'd REALLY, pretty please, with a cherry on top :), can I/we have a new release/tag cut with the updated dependency on embedded-io (and embedded-io-async in the case of embassy-sync?

It's available in the latest commits, but I'm trying to publish my own libs, but cargo package seems to not want to accept a GIT revision :(.

In my main program, I need to use defmt-serial from a GIT repo, because the released version can't handle later Embassy versions. Which causes it to bring in v0.7.1.. Which causes the double deps.

However, my libs don't, so they're fine with the released versions of Embassy. BUT, if I update them to the released versions of Embassy, I need to do so in my main app as well, which ... well, causes all this :(.

cargo-tree.txt

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions