sanisoclem / calcver-cli Goto Github PK

see setup of: https://github.com/johannhof/difference.rs

todos:

• check that the crate is usable will be tracked by #6
• ~archive the calcver-rs project~~
• move remaining issues to this repo
• move badges to this repo
• bump minor version to 0.3 (to supersede any old crates)

document the version calculation

appveyor

If the caller passes a subdir of a git repo, the program doesn't find the root path and will panic instead.
Not sure if this should be fixed,

moved from https://github.com/easy-semver/calcver-rs/issues/10

1. Check if there are pending changes to repo (bypass if --ignore-pending set)
1. Terminate if there are pendings changes

1. Do any version update actions (see #9)
2. Commit any changes
3. Tag latest commit with correct version

• restructure modules (was written with C# classes in mind)
• remove release flow (won't write to cargo toml, instead write results to stdout)
• use traits to get version information from a repository

tldr; use idiomatic rust

Packaging native binaries as a dotnet global tool is not yet supported: https://github.com/dotnet/cli/issues/9488#issuecomment-397166215

Since support for this is not yet planned for any release, will set this on hold and re-implement in C# internally.

simplified version:

# -- uncomment to override defaults
#root: .
#repository_type: git
#prerelease_prefix: alpha
#tag_regex: \d+\.\d+\.\d+
#major_regex: "BREAKING CHANGE:"
#minor_regex: ^feat
#patch_regex: ^fix
cargo: .\cargo.toml
actions:
  - .\bin\update-version.cmd #dummy update version for testing only

release.rs currently have no tests. Since these functions have side effects, maybe I should write integration tests.

todo: define tests

allow version to be written to file(s) by:

• common formats
  • cargo.toml
• run script
  • set CALCVER_VERSION

not critical for v1 release since all changes are local

maybe use build scripts? https://doc.rust-lang.org/cargo/reference/build-scripts.html#case-study-code-generation

@joelleortiz thoughts? ironic no?