I wanted to investigate an issue, but found that I although was using 1.0.9 from crates.io but there wasn't a corresponding git tag.
Normally, cargo puts a .cargo_vcs_info.json in the generated .crate file, if the release is made from git. Investigating the .crate file I think the release was made roughly from 3751785. The only difference (apart from changes made to Cargo.toml by cargo publish) is a one-line change to .gitignore.
Was 1.0.9 made from a dirty git working tree? I recommend the use of automated tooling for releasing which checks things like "is the git tree clean" and also makes the tags.
To remedy this, I suggest: make a temporary git branch containing this delta
I wanted to investigate an issue, but found that I although was using 1.0.9 from crates.io but there wasn't a corresponding git tag.
Normally,
cargo
puts a.cargo_vcs_info.json
in the generated.crate
file, if the release is made from git. Investigating the.crate
file I think the release was made roughly from 3751785. The only difference (apart from changes made toCargo.toml
bycargo publish
) is a one-line change to.gitignore
.Was 1.0.9 made from a dirty git working tree? I recommend the use of automated tooling for releasing which checks things like "is the git tree clean" and also makes the tags.
To remedy this, I suggest: make a temporary git branch containing this delta
and tag it
1.0.9