I'm currently packaging cargo-edit for voidlinux, and while compiling the package locally for testing I noticed that the v0.3.2 tag points to a commit where the version in Cargo.toml is still 0.3.1. I'm not sure how to fix that, retagging would probably not be the way, but for future versions it would be nice if you could make sure those two actually match.
Yeah, sorry, I screwed up. The only difference is the version bump though.
Oh, that is indeed unfortunate!
I'll have a look at #309 right now and maybe release 0.3.3 soon. I'll ping you.
@ordian no worries, shit happens :D
I'll just include a patch file with the package for this release.
Sorry to hijack this issue -- @ordian, I looked at #309 and made some adjustments. I think we should merge this when travis is green. I've also made https://github.com/killercup/cargo-edit/commit/3e9994fad7965d120c415b3b97c39c031dc1a892 but GitHub doesn't let me open a PR (throws a 500 instead). What do you think of this?
Feel free to ping me on discord or gitter for more direct communication :D
Am 20.06.2019 um 10:21 schrieb Jan Christian Grünhage notifications@github.com:
@ordian no worries, shit happens :D
I'll just include a patch file with the package for this release.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
@killercup check out gitter :)
@jcgruenhage published 0.3.3 with updates to the latest dependencies and the correct version in Cargo.toml: https://github.com/killercup/cargo-edit/releases/tag/v0.3.3
I've submitted 0.3.3 to the void repo now :+1: Thanks for fixing this so quickly!