Closed jtk54 closed 7 years ago
@jtk54 which version of clog
are you using?
clog 0.9.2, I just did a fresh install of rust and cargo this morning, and used cargo install clog-cli
.
If it helps, rustc
is at 1.14.0 (e8a012324 2016-12-16) and cargo
is at 0.15.0-nightly (298a012 2016-12-20).
Still seeing this issue, do you need more information to debug? Are you able to reproduce?
Sorry, I had some other issues and work come up! I'll see if I can reproduce it tonight when I get home. Also, do you have any .clog.toml
in use?
No worries, just checking in. I'm not using a .clog.toml
to specify output.
Following up on this. I just compiled clog
locally from source to try and reproduce the issue with --setversion
I was seeing and everything was working fine.
This makes me think that the clog
artifact published to the cargo
registry is out of date. When I installed with
cargo install clog-cli
the setversion
issue persists. When I clone the git repo and install from HEAD using
cargo install
from the root directory, everything works properly. Let me know if you can reproduce this. For now, everything is good on my end -- I'll remember to install from source : D
I just pushed a new version to crates.io so hopefully that fixes this! Let me know if this issue persists. Sorry for such a long wait!
Bumping up to clog 0.9.3 from crates.io worked for me, thanks for following up : D
Running
clog
on Ubuntu (3.13.0-105-generic #152-Ubuntu SMP Fri Dec 2 15:37:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux) with--setversion
doesn't set the version in the changelog.Sample command:
clog -r <REPO> --from <HASH> --setversion 1.7.0 | less
Expected:
Actual:
Using the minor version flag
-m
worked fine, but I want to use a different version format in the changelog output than what the git tags look like. I can always manually add the version in, but it would be nice to automate this.