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
Should the --workspace flag be enabled by default when running in a workspace?
Right now, running cargo semver-checks check-release in a workspace will only check the top-level crate in the workspace, if there is one. It might not be obvious to users that this is the case, and it's plausible that users might not know that they need to add a flag like --workspace to check other crates as well.
The text was updated successfully, but these errors were encountered:
This is the same behavior as native cargo commands that operate on packages when run in a workspace. Commands like cargo update and cargo clean operate exclusively on the workspace level and don't take a flag.
Should the
--workspace
flag be enabled by default when running in a workspace?Right now, running
cargo semver-checks check-release
in a workspace will only check the top-level crate in the workspace, if there is one. It might not be obvious to users that this is the case, and it's plausible that users might not know that they need to add a flag like--workspace
to check other crates as well.The text was updated successfully, but these errors were encountered: