Note: Some changes are technically breaking changes, although it's highly unlikely that people are going to be affected. According to SemVer, below 0.x everything goes, so this would be acceptable from a spec point of view.

However, I could also change the version number to 0.9.0 instead.

IMO I think it's ok to release as 0.8.1 - this crate gets few downloads on crates.io. If upgrading to the latest stm32l0xx crate (waiting on stm32-rs/stm32-rs#659 to be released) is also a breaking change, that might be a good point to release 0.9.0?

According to SemVer, below 0.x everything goes, so this would be acceptable from a spec point of view.

I think what's more relevant to us, is how Cargo implements SemVer. And Cargo treats 0.8.1 as compatible to 0.8.0.

I don't see a reason to cut corners here. Just call it 0.9.0. If we want to release 0.10.0 in 2 weeks, so be it.

I'm sure people will have lockfiles in their firmware projects. Nevertheless, it doesn't hurt to bump to 0.9, we could also release 0.137 next week and it would still be OK 🙂

I'll create a replacement PR.

-> #207