0.14.0 (2024-02-04)
Breaking Changes
Cargo.toml files must now have a package.name property
This was already required by Cargo, but wasn't enforced by Knope until now. Before, a Cargo.toml file like
[package]
version = "0.1.0"was acceptable, but now it must be
[package]
name = "my-package"
version = "0.1.0"Features
Add basic Cargo workspace support
If you have a Cargo.toml file in the working directory which represents a Cargo workspace containing fixed members, like:
[workspace]
members = [
"my-package",
"my-other-package",
]then Knope will now treat each member like a package.
There must be a Cargo.toml file in each member directory, or Knope will error.
This doesn't work with path globbing yet, only manual directory entries. See the new docs for more details.
Use default packages/workflows even when knope.toml exists
If you define a knope.toml file without any packages, Knope will assume the default packages (as if you had no knope.toml file at all).
Likewise, if you have no [[workflows]] in a knope.toml file, Knope will assume the default workflows.