Release 0.17.0

[fw-immunant]

• Fixes Update crates.io release #690.

This has been a long time coming, but we've now merged all the dep updates and gotten our release process in shape.

[fw-immunant]

Hoping to make the release late Monday if no issues crop up.

[kkysen]

There are a few things missing from this. Published packages require description, license/license-file, and documentation/homepage/repository fields, which most of the new packages don't have. To fix part of this, I opened #804, which also unifies package versions, which makes this PR simpler. #805 then adds the package descriptions.

Also, I don't think we should bump version numbers for the unmaintained packages, namely c2rust-macros and c2rust-refactor. I don't think we should publish new versions of them if they are unchanged and unmaintained.

I'm also not sure the update-versions.sh script is the best idea vs. something much more polished and widely used like cargo-release. cargo-release should get all the little details right that this script probably won't. For example, it immediately detected that we're missing a bunch of the required package fields for publishing. If there's a suitable alternative that's fairly widely used, I think that's better than our own script that we'll have to maintain, which also adds dependencies on things like sponge.

Regardless, I think we should merge #804 first, which then simplifies this PR, and also open a PR that includes descriptions for all of the new packages (#805).

[fw-immunant]

Sharing versions via workspace inheritance breaks the script anyway, so I've removed it. I also couldn't get cargo-release to do the right thing, trying cargo release minor and cargo release --workspace minor and also the --dependent-version=upgrade flag.

[fw-immunant]

I think we should bump version numbers for all crates in the repo to avoid divergence. If we want to delete the c2rust-refactor and c2rust-macros crates entirely, we can--they'll still be in the history. We don't need to release old, deprecated crates on crates.io, nor do I think it makes sense to release the new analysis/runtime/pdg crates; they aren't in any state where it would be a good idea to get them from crates.io rather than GitHub. We should release just these crates:

• c2rust
• c2rust-asm-casts
• c2rust-ast-builder
• c2rust-ast-exporter
• c2rust-ast-printer
• c2rust-bitfields
• c2rust-bitfields-derive
• c2rust-build-paths
• c2rust-transpile

[kkysen]

I think we should bump version numbers for all crates in the repo to avoid divergence. If we want to delete the c2rust-refactor and c2rust-macros crates entirely, we can--they'll still be in the history.

Not sure it's the best idea, but I don't think it really matters either way. They were bumped to 0.16.0 even after being retired anyways.

We don't need to release old, deprecated crates on crates.io

👍

nor do I think it makes sense to release the new analysis/runtime/pdg crates; they aren't in any state where it would be a good idea to get them from crates.io rather than GitHub.

👍

We should release just these crates:

• c2rust
• c2rust-asm-casts
• c2rust-ast-builder
• c2rust-ast-exporter
• c2rust-ast-printer
• c2rust-transpiler
• c2rust-bitfields
• c2rust-bitfields-derive
• c2rust-build-paths
• c2rust-transpile

👍 , except I think there's a typo in c2rust-transpiler (duplicate/nonexistent)

[kkysen]

One minor nit, but otherwise I think it's all good for a release now!

[kkysen]

Usually version goes before path and there's no space before the ,.

[kkysen]

Sharing versions via workspace inheritance breaks the script anyway, so I've removed it.

👍

I also couldn't get cargo-release to do the right thing, trying cargo release minor and cargo release --workspace minor and also the --dependent-version=upgrade flag.

cargo release version minor at least worked for upgrading the versions and dependencies for me, though it doesn't upgrade them in non-workspace packages like the analysis/tests/ or tests/ crates.