0.17.0 - 2024-05-18
Added
cargoDoc
now supportsdocInstallRoot
to influence which directory will be
installed to$out/share
(which can be useful when cross-compiling). By
default$CARGO_TARGET_DIR
and$CARGO_BUILD_TARGET
(if set) will be taken
into accountcrateNameFromCargoToml
now supports selecting a derivation name by setting
package.metadata.crane.name
orworkspace.metadata.crane.name
in the root
Cargo.toml
vendorCargoDeps
,vendorCargoRegistries
,vendorGitDeps
, and
vendorMultipleCargoDeps
now support arbitrary overrides (i.e. patching) at
the individual crate/repo level when vendoring sources.
Changed
- Breaking
cargoAudit
no longer acceptscargoExtraArgs
(since it does
not support the regular set ofcargo
flags like most cargo-commands do, it
does not make much sense to propagate those flags through) buildTrunkPackage
now setsenv.TRUNK_SKIP_VERSION_CHECK = "true";
if not
specified
Deprecations
- In the future,
crateNameFromCargoToml
will stop considering
workspace.package.name
in the rootCargo.toml
when determining the crate
name. This attribute is not recognized by cargo (which will emit its own
warnings about it) and should be avoided going forward. - In the future,
crane.lib.${system}
will be removed. Please switch to using
(crane.mkLib nixpkgs.lib.${system})
as an equivalent alternative.