Releasing a new version

[zesterer]

Several PRs were merged recently that add a significant number of features to the crate. A new version for crates.io would be welcome.

[mvdnes]

Sure. Do you want to publish 0.5.3 or 0.6.0?

[zesterer]

0.6.0. Although I don't think that any changes are actually breaking, adding support for lock_api and changing up the internals quite a bit calls for a new minor version in my view. If it's easier for you, I'm happy to handle the release (I'll need permission on crates.io, of course).

[mvdnes]

Sure, I have sent you an invite.

[zesterer]

Thanks! I'll release the new version in a little while.

Edit: 0.6 is now released!

[ErichDonGubler]

Does this mean that RUSTSEC-2019-0031, which states this project is unmaintained, is invalid? I've been pinged on a PR I have that resolves that advisory for ring, where the 0.6.0 release was noted.

[zesterer]

@ErichDonGubler Yes, it's invalid. I files a PR to update this 2 days ago. It was merged, but it seems there's a bug in cargo-audit that means it still shows up. Hopefully this will be fixed soon.

[zesterer]

@mvdnes If you happen to have the time, I'd much appreciate a change of the repo description to Spin-based synchronization primitives since I don't seem to have permission to change it. Cheers!

[mvdnes]

👍 Done

[djc]

It was merged, but it seems there's a bug in cargo-audit that means it still shows up. Hopefully this will be fixed soon.

Can you link to the bug? I looked for it but haven't found it.

[zesterer]

@djc It was discussed on the rust-lang Zulip. this PR should have resolved it though.