Missing release tag for 1.2.0

[panicgh]

https://crates.io/crates/keepass-diff/versions shows that there is already a 1.2.0 release, but this git repo does not contain a corresponding tag. It would be nice if the respective commit was tagged.

[mrghosti3]

@Narigo
crates.io is now showing v1.2.0 so this issue is resolved.

[Narigo]

I think the issue is that I forgot to add a tag to the Git which commit is the 1.2.0 version. I need to add this here still. Thanks for the heads-up btw @panicgh !

[mrghosti3]

Since that version is uploaded to crates.io the issue can be closed.

[panicgh]

I don't know rust. How can I verify from which git commit a crates.io artifact comes from?

[mrghosti3]

Huh, apparently v1.1.4 is also missing from the git main branch.

@Narigo could you add both v1.2.0 and v1.1.4 tags when you will be available?

[Narigo]

@mrghosti3 do you happen to know a good way how to find out on which commit the publish has been done? 😬 I'm pretty sure I always did do publish on a commit, but I missed tagging them. I'm sure I did some additional Readme / doc commits after the last publish so I need to find out which one was the actual one.

My idea would be to download the version from crates.io and manually check those commits against it. Is that the best idea or is there a tool out there which can do this for me? 😬 It sounds like a pretty time consuming process and as one can see in my activities, keepass-diff is not my top priority currently...

[mrghosti3]

I'd suggest scanning through the git history for changes in Cargo.toml. This may not give the exact commit when publish was done, but it will eliminate a lot of the other commits. Maybe looking into some commits after you could tag them as definitive version release?

Command for that in bash I use:

$ git log -p Cargo.toml

You could the search for keywords like version in the pager.

[Narigo]

Hey, someone scanned all the repos and put it online: https://news.ycombinator.com/item?id=40698536

There is keepass-diff@1.2.0 in there as well:

Does that mean I can safely tag this commit with 1.2.0 then? 08344c5 😅

I'm sorry there is so much going on here, I didn't even get around to fix this and look into all the issues lately

[mrghosti3]

Hey, someone scanned all the repos and put it online: https://news.ycombinator.com/item?id=40698536

There is keepass-diff@1.2.0 in there as well:

Does that mean I can safely tag this commit with 1.2.0 then? 08344c5 😅

I'm sorry there is so much going on here, I didn't even get around to fix this and look into all the issues lately

I pulled the .crate (which is just .tar.gz) file from crates.io and diffed the contents. The only differences is in their version of Cargo.tom, which generated by cargo, and some other configs. But the code, docs, tests and even the lock files match up with the commit you specified. I do believe, that commit 08344c5 is the right one to tag as v1.2.0.