Prepare a release for cyclonedx-bom 0.8.1

[grahamc]

After #844 and #845 I'd be glad for a release. I thought submitting the (small) changelog might be a help there :).

As I mentioned in a comment on #845, I already pinned my project to a revision. That means this isn't critical to me if you're not ready to ship a release. But I wouldn't mind the tidyness.

Thank you again!

[grahamc]

...d'oh ... I have other files to include in this commit.

[grahamc]

Ideally this waits for #847

[Shnatsel]

I understand we need the semver bump because spdx crate is present in the public API? I can never remember which crates we expose and which we keep hidden.

[grahamc]

I'm not real sure, but I think it is reasonable with the MSRV bump?

[Shnatsel]

An MSRV bump alone shouldn't be semver-breaking. Cargo has an MSRV-aware resolver that can select the latest MSRV-compatible version automatically.

[grahamc]

I think this is ready to rock, what do you think @Shnatsel?

[Shnatsel]

Thanks! This certainly helps!

I'd like publish new versions of cyclonedx-bom and cargo-cyclonedx together if I can.

We need to wrap up #777 still. @beer4code was interested in taking it over.

[Shnatsel]

You know what, nevermind. #777 is tricky because the spec is so vague about what goes there, so I don't want to block the next release on it.

[grahamc]

Cool! Is there anything left for me to help you finish this out?