Most recent release diverges between github and crates.io #627

Activity

1. Xuanwo commented on Sep 11, 2025

   

   Xuanwo

   on Sep 11, 2025

   Member

   More actions

   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?
2. AdamGS commented on Sep 11, 2025

   

   AdamGS

   on Sep 11, 2025

   ContributorAuthor

   More actions

   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)

   👍React with 👍1Reacted by Xuanwo
3. Xuanwo commented on Sep 11, 2025

   

   Xuanwo

   on Sep 11, 2025

   Member

   More actions

   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.

   👍React with 👍2Reacted by Adam Gutglick and Ben Beasley