v0.16.5

See v0.16.6

v0.16.4

See v0.16.6

v0.16.0

Added

• Git dirty check for submodules #277

Changed

• Prior sharing of pushes between workspace crates is now behind the flag consolidate-pushes #276

Fixed

• Avoid panic on invalid Cargo.toml entry #275

v0.13.0

Added

• Notify users on unchanged crates when releasing workspace [#148]
• Strict check on replacements [#187]
• Trace replacement diff on dry-run [#171]
• Allow workspace release commits to be consolidated [#181]
• Releasing specific version [#191]
• tag_name is now available in replacements and can be useful for changelog generation in multi-crate workspace [#168]

Changed

• Renamed option "pro-release-commit-message" to "post-release-commit-message" [#140]
• Use logging for output [#152]
• Also check untracked files in initial dirty check [#146]
• [package.metadata.release] in $CRATE/Cargo.toml now has a higher priority than $CRATE/release.toml [7cc9890] [#181]
• Confirmation is prompted for even when there is no version bump [47bf645] [#175]

Fixed

• Fixed issue when crate.io didn't update in time that causing workspace release failed [#183]

Removed

• Doc upload removed as the community has moved to docs.rs [#176]

0.9.0

What's new with cargo-release 0.9:

• New pre-release-hook allows you to run a hook before release process. If the hook returns a non-zero code, the release process is aborted.
• Tags now pushed in a standalone git push, which is compatible with services like AppVeyol #43
• Skipping publish if configured #39
• Added {{date}} support for pre-release-replacements
• Fixed issue when using cargo-release on Windows #48
• Fixed issue with colors #41