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
When I try to unify the dependencies of autonomys/subspace@03d11c7 , some renamed dependencies aren't properly declared in the workspace Cargo.toml.
For example, name attributes should be added in the workspace, but aren't added for:
local dependency domain-client-block-preprocessor, which is actually named domain-block-preprocessor in the crate: autonomys/subspace@4b3ef41
crates.io dependency codec, which is actually named parity-scale-codec in the registry: autonomys/subspace@912cc97
In both cases, the links show us manually unifying the names (rather than automatically adding a name attribute, which is what cargo autoinherit should do).
This might only happen when the dependency is present under two different names in the workspace, for example, in autonomys/subspace#3411
The text was updated successfully, but these errors were encountered:
When I try to unify the dependencies of autonomys/subspace@03d11c7 , some renamed dependencies aren't properly declared in the workspace Cargo.toml.
For example,
name
attributes should be added in the workspace, but aren't added for:domain-client-block-preprocessor
, which is actually nameddomain-block-preprocessor
in the crate: autonomys/subspace@4b3ef41codec
, which is actually namedparity-scale-codec
in the registry: autonomys/subspace@912cc97In both cases, the links show us manually unifying the names (rather than automatically adding a
name
attribute, which is whatcargo autoinherit
should do).This might only happen when the dependency is present under two different names in the workspace, for example, in autonomys/subspace#3411
The text was updated successfully, but these errors were encountered: