release: review public APIs for next release, 0.5.0 with breaking changes

[chris-oo]

Some of the methods most likely do not need to be pub. As part of taking zerocopy 0.8.x, this will require a semver breaking change update, so use this chance to do a sweep of the public methods and remove any that aren't necessary.

[CookieComputing]

Hi there! Just wondering if there was a timeline for a 0.4.0 release, as it seems like in 0.3.4 the zerocopy semver upgrade unfortunately didn't make it in, so the svsm project still needs to reference this dep separately. I imagine the svsm project will also need to make some upgrade as well after 0.4.0 is changed right?

[chris-oo]

Yeah. I haven't had time to do a public method sweep so perhaps I may try to just publish a 0.4.0 release for the zerocopy update and push this to a 0.5 update. Let me see if I can get to that next week.

FWIW in openvmm, we are just consuming via git hash to pickup the latest zerocopy changes.

[CookieComputing]

Thanks! Our build system is referencing the crate via crates.io. While I can force it to consume via the git hash, the Rust toolchain maintainers would much rather I import a crate with semver 😅

[chris-oo]

That's fair, I'll see if i can get to this next monday.

[chris-oo]

See #93 . Once that's in I'll make a release tag and push to crates.io.

[chris-oo]

Should be available on crates.io now.

[chris-oo]

Note to self the next release must be a breaking change, as there are PRs in flight that will change the definition of existing structures (like sev_vmsa) #109