Most recent release diverges between github and crates.io

[AdamGS]

Looking at the most recent release:

• Most recent GitHub tag is 1.0.0, pre-1.0 the most recent release is 0.16.5
• On crates.io, most recent release is 0.17, which isn't tagged on GitHub (I assume that's 1.0?)

[Xuanwo]

Hi, thank you @AdamGS for checking out reqsign!

Actually, I made a mistake earlier—I'd like to tag the repo with reqsign-core, since reqsign is just the facade crate we expose to users.

So here's the plan:

• reqsign-core: v1.0.0
• reqsign-aws-v4: v1.0.0
• ...
• reqsign: v0.17

Maybe we should just release reqsign as v1.0.0 to make things clearer?

[AdamGS]

I guess it mostly depends on your semver guarantees (or any other versioning scheme).
If both are in this repo - you can also release both as a GitHub release, which will make the difference clearer (at least to me)

[Xuanwo]

I guess it mostly depends on your semver guarantees (or any other versioning scheme). If both are in this repo - you can also release both as a GitHub release, which will make the difference clearer (at least to me)

You are right. I'm thinking of release tag like reqsign-core v1.1.0, reqsign v0.17.0 and reqsign-aws-v4 v1.0.1. I think that will be helpful.