Version and linkage foo between crates.io and GitHub

[cdbrkfxrpt]

Hi,

thanks for the crate, great work. However I noticed some things:

• on crates.io, this is listed as v0.5.0 and it links to another fork of this GitHub repo
• said fork is tagged only up to v0.4.0 and depends on defmt v0.1.3 and therefore breaks builds with the current recommended version of defmt, i.e. v0.2.0
• this creates dependency hell because docs of defmt, examples, etc all are geared to be compatible with defmt v0.2.0
• this GitHub repo here depends on defmt v0.2.0 already, but that is not of importance since crates.io does not link here

Is it fair to assume that this here is the active development crate? If that is the case, may you point crates.io in the right direction, please? While at it, a release for 0.5.0 could be created here as well.

I'm sorry to have to bother you with this, but I don't see how I could fix this myself.

Cheers

[cdbrkfxrpt]

Forget what I said, the problem is that stm32f1xx-hal is depending on bxcan-0.4.0.