Bump minor version (0.8.0 --> 0.8.1, publish to crates.io)?

[smklein]

First of all, thanks for patching the fixes triggered by Cargo audit, and generally maintaining this crate. It has been super useful for me, and I appreciate all the work you've done in keeping it up-to-date!

When fixes for "cargo audit" are patched into bollard without a corresponding minor release, projects which depend on bollard are still triggering audit issues. As an example, a "needs-bollard" binary that uses version 0.8.0 (released Aug 23, 2020) will still trigger RUSTSEC-2020-0036 and RUSTSEC-2020-0053, so although "cargo audit" would succeed for "bollard", it would fail for "needs-bollard".

This is admittedly a low-priority issue - our workaround is to pass the "--ignore=ISSUE" flag to audit, and wait for a new release of Bollard, but just figured I'd mention it - if a new minor release of bollard came out, this would help us remove these workarounds.

[fussybeaver]

Hi ... I am planning to do a release soon, but there's a couple of outstanding issues:

• macos failure in the prune volume test case
• macos integration test running green in Github Actions
• some testing in downstream projects like Docuum and Vector

[jamtur01]

@fussybeaver Happy to help with the Vector testing. I'm waiting on a fix for https://github.com/timberio/vector/issues/4169 (the change from an enum to a string for logging plugins) in the next release.

[jamtur01]

@fussybeaver Testing at master for bollard in Vector with some sample configurations looks good to me.

[fussybeaver]

That's really useful thanks @jamtur01