v0.18.1

[0.18.1] - 2021-10-09

Fixed

• Introduced cargo publish fix for workspaces that was meant to be in before 0.18

v0.18.0

[0.18.0] - 2021-10-08

v0.17.1

[0.17.1] - 2021-08-24

Fixed

• Correctly detect changes for crates outside of the root

v0.17.0

Thanks to byron and pksunkara for the collaboration between cargo-release, cargo-smart-release, and cargo-workspace-publish that contributed to this release.

Features

• Pre-built binaries
• Add allow-branch config setting to limit what branches a release can happen from
• Run cargo publish during dry-runs to help catch publish-specific errors
• Support Cargo.tomls workspace.metadata
• Support ~/.config/cargo-release/release.toml

Fixed

• In theory, finally fixed it so we properly wait between publishing of crates in a workspace
• Correctly update dependents on post-release version bump.
• Specifying --package should switch us to opt-in
• Don't warn a user about releasing a crate without changes if a dependency changed
• Notify for all [[bin]] crates on Cargo.lock change, rather than just the root crate
• Made clearer what are fatal errors during dry-run (since dry-run doesn't stop for them)
• Gracefully handle path-only dependencies which are especially important for cycles.
• Log what was dirty about a repo to make it easier for people to report problems
• Allow pushing even when there isn't a tracking branch

Breaking Changes

• --dry-run is now the default. Pass --execute to perform the release.
• exclude-paths config setting was removed; we now rely on cargo package --list to know which files to check for changes.

v0.16.6

Yanked, broke compatibility

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