All Versions
57
Latest Version
Avg Release Cycle
13 days
Latest Release
215 days ago
Changelog History
Page 1
Changelog History
Page 1
-
v0.23.0 Changes
November 05, 2022๐ฅ Breaking Changes
- ๐ No longer assume
package.publish = false
also means that releases are disabled (#597)
- ๐ No longer assume
-
v0.22.4 Changes
November 05, 2022๐ Fixes
- Skip remote check if not pushing
-
v0.22.3 Changes
November 05, 2022๐ Fixes
- Ensure pushes are atomic
-
v0.22.2 Changes
October 31, 2022๐ Fixes
- Limit rate-limiting to crates being published
-
v0.22.1 Changes
October 21, 2022๐ Fixes
- Don't claim the user excluded a crate when the config did
- Actually push the branch
- ๐ Show we'll push the branch in dry-run mode, even if we won't as its better than not showing it even if we will
-
v0.22.0 Changes
October 21, 2022Highlights
๐ The goal of this release is improved workspace support, including
- ๐ฆ Workspace inheritance support
- ๐ Greater control over versioning by supporting calling
cargo release version
as needed and thencargo release --unpublished
- ๐ง Setting configured crate owners when publishing new crates
- ๐ Identifying failures early like missing metadata, hitting rate limits, etc
- ๐ Inspect changes with
cargo release changes
, including conventional commit support - ๐ Improved defaults
๐ This does mean that
cargo release
(no other args) changed from recovering ๐ from a failed release to releasing the currently specified versions of crates. ๐ Recovery is now done more manually withcargo release publish
, etc.๐ฅ Breaking Changes
- โ Removed
dev-version
support - 0๏ธโฃ
consolidate-commits
is now the default for workspaces- It is also now all-or-nothing
consolidate-pushes
is now exclusively used- โฌ๏ธ
dependent-versions = "upgrade"
is now the default- Removed
ignore
,warn
, anderror
- Removed
- ๐
Cargo.toml
'spackage.publish = false
disables release - โ Removed
--dump-config
in favor ofcargo release config
- โ Remove
--token
in favor in favor of more secure ways of authenticating - ๐
cargo release
is no longer used for recovery, instead usecargo release publish
,cargo release tag
, etc - ๐ Error if nothing to release
- ๐ Changed standard exit code to 101
Compatibility
MSRV is now 1.64.0
๐ Fixes
- โ Turn some verification errors into warnings on steps
- โ Run replacements when no version is bumped
- Be smarter about finding previous tags
- Bail out early when we'll hit crates.io rate limits
- Bail out early when we'll hit
cargo publish
missing field errors - ๐ฆ Implicitly layer package over workspace for workspace config when not in a workspace
- โก๏ธ Only update versions for path dependencies
- Cleaned up output
- โ Ignore tests when tracking changes
๐ Features
- ๐ฆ
package.version.workspace = true
support- Forces
consolidate-commits = true
- Forces
shared-version = "workspace"
- Forces
- ๐
dependency.<name>.workspace = true
support - ๐ฆ
package.publish.workspace = true
support owners = []
to set crate owners for new workspace members- Use
cargo release owner
to update owners for existing crates
- Use
- ๐ In addition to
shared-version = true
, we now support named groups, likeshared-version = "foo"
- ๐
--unpublished
flag to automatically release unpublished crates - ๐ฆ Expose
changes
,hook
, andcommit
steps
-
v0.21.4 Changes
October 14, 2022๐ Fixes
- ๐ Fail again when pre-release checks fail
-
v0.21.3 Changes
October 13, 2022๐ Features
- ๐ Expose release steps as subcommands, useful for
- Custom release processes
- Verify configuration / cargo-release behavior
- Recovering on failure
- ๐ Expose release steps as subcommands, useful for
-
v0.21.2 Changes
September 28, 2022๐ Fixes
- ๐ Polish help output
-
v0.21.1 Changes
July 12, 2022๐ Fixes
- Load workspace config from the actual workspace manifest