Ning Sun

@junmer 赞，核心技术！

@rapiz1 I'm no longer working on this. So feel free to pick it up for further development. Using feature flag for rustls makes a lot of sense. Thank you!

As maintainer of [handlebars-rust](https://github.com/sunng87/handlebars-rust), I had similar thoughts when designing replacements so I decide to use double-bracket variables, which is compatible with handlebars and many languages . The only downside...

Nice, we can call semverver to give user a suggestion on release level

I haven't got time to looking into detail with rust-semverver. I really wish it can provides an output format that friendly for other tools to parse.

@ibabushkin rust-semverver would be a too big dependency to cargo-release. I still recommend a programmer friendly output option for rust-semverver. For example `cargo semver --compact` that output the suggested version...

at the moment, you can * `cargo release alpha` to bump version from `alpha.0` to `alpha.1` * `cargo release beta` to bump version from any `alpha` to `beta` * `cargo...

@epage Yes. Because Github releases has release notes included, for example: https://github.com/open-telemetry/opentelemetry-java/releases/tag/v0.9.1 We will have to upload release notes of a particular version, see `-n` and `-F` option in [gh...

I just realized there is a specification about conventional commit message: https://www.conventionalcommits.org/en/v1.0.0/ . It is designed to generate changelog from commit message. We can first provide commit message generation for...

Great! Sounds like we can provide an option, say `changelog=conventional`, to generate changelog from conventional commit messages. The changeset can also be hold in our context for replacement and hooks.