0.6.0 - 2022-09-07
Added
- Added
cargoNextest
for running tests via cargo-nextest - Added
cargoAudit
for running cargo-audit
with a provided advisory database instance.
Changed
- Breaking: the
--workspace
flag is no longer set for all cargo commands
by default. The previous behavior can be recovered by settingcargoExtraArgs = "--workspace";
in any derivation. - Breaking: the
$CARGO_PROFILE
environment variable can be used to specify
which cargo-profile all invocations use (by defaultrelease
will be used).
Technically breaking if the default command was overridden for any derivation;
setCARGO_PROFILE = "";
to avoid telling cargo to use a release build. - Breaking:
cargoTarpaulin
will use the release profile by default - Breaking:
cargoClippy
'scargoClippyExtraArgs
now default to
"--all-targets"
instead of being specified as the cargo command itself. If
you have setcargoClippyExtraArgs
to an explicit value and wish to retain
the previous behavior you should prepend"--all-targets"
to it. - Breaking:
remapSourcePathPrefixHook
and thedoRemapSourcePathPrefix
option have been removed, and the behavior ofbuildPackage
has been updated
to break false dependencies on the crate sources from the final binaries
(which was the old behavior of thedoRemapSourcePathPrefix
option). To
disable this behavior, set thedoNotRemoveReferencesToVendorDir
environment
variable to any non-empty string. - All cargo invocations made during the build are automatically logged
- Vendoring git dependencies will throw a descriptive error message if a locked
revision is missing fromCargo.lock
and a hint towards resolution
Fixed
- Breaking:
vendorGitDeps
will only include crates referenced by the
Cargo.lock
file, meaning any extraneous crates which happen to be present in
the git repository will be ignored.