-
-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add tests for publish = false
workspace members explicitly included with --package
#866
Add tests for publish = false
workspace members explicitly included with --package
#866
Conversation
e8838e6
to
14397e9
Compare
Now based on #867, compare link |
14397e9
to
a0c0a37
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, happy to merge after #867.
/// Running `cargo semver-checks` on a workspace with a `package = false` member, | ||
/// explicitly including that member with `--package` and also specifying `--workspace`. | ||
/// Currently, `--workspace` overrides `--package` and the `publish = false` member is not | ||
/// semver-checked, and `cargo-semver-checks` silently exits 0. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would you mind opening an issue to make this consistent with just specifying `--package, and linking to it here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See #868.
"--manifest-path", | ||
"test_crates/manifest_tests/workspace_all_publish_false/new", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another interesting question: what happens if we have --manifest-path test_crates/manifest_tests/workspace_all_publish_false/new/a/Cargo.toml
?
Then we explicitly point to the package's manifest, ask for the workspace, then ask for the package itself.
Happy to accept this in a separate PR.
a0c0a37
to
0f9bcc1
Compare
Just added a couple of our PR review notes as source code comments, to make our thinking on the subject easier to find in future iterations. |
Tests the two behaviors described in #859 (comment).
They are currently not consistent (
--workspace --package xxx
doesn't semver-check and--package xxx
does).