You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 setting cargoExtraArgs = "--workspace"; in any derivation.
Breaking: the $CARGO_PROFILE environment variable can be used to specify
which cargo-profile all invocations use (by default release will be used).
Technically breaking if the default command was overridden for any derivation;
set CARGO_PROFILE = ""; to avoid telling cargo to use a release build.
Breaking: cargoTarpaulin will use the release profile by default
Breaking: cargoClippy's cargoClippyExtraArgs now default to "--all-targets" instead of being specified as the cargo command itself. If
you have set cargoClippyExtraArgs to an explicit value and wish to retain
the previous behavior you should prepend "--all-targets" to it.
Breaking: remapSourcePathPrefixHook and the doRemapSourcePathPrefix
option have been removed, and the behavior of buildPackage has been updated
to break false dependencies on the crate sources from the final binaries
(which was the old behavior of the doRemapSourcePathPrefix option). To
disable this behavior, set the doNotRemoveReferencesToVendorDir 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 from Cargo.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.