Skip to content
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

Adding feature-flags to release configuration #75

Merged
merged 2 commits into from
Jan 29, 2019

Conversation

spacekookie
Copy link
Contributor

This PR adds features and all_features as both flags to the CLI
as well as the release.toml configuration. This change allows you
to tell cargo-release to verify the package with certain features
enabled, in order to avoid needing to use no-verify for crates
that depend on certain features being enabled (or simply any
feature) before they can be uploaded.

This change is dependent on rust-lang/cargo#6453, which adds this
feature to the base cargo publish command.

The motivation behind this PR is the same as the above mentioned
cargo PR: reducing the amount of packaging errors that can happen
due to people not being able to verify their code because it has
some feature requirements for compilation, ultimately resulting in
a more healthy package ecosystem.

@sunng87
Copy link
Collaborator

sunng87 commented Dec 17, 2018

LGTM. Could you please also update README for new options?

This PR adds `features` and `all_features` as both flags to the CLI
as well as the `release.toml` configuration. This change allows you
to tell `cargo-release` to verify the package with certain features
enabled, in order to avoid needing to use `no-verify` for crates
that depend on certain features being enabled (or simply any
feature) before they can be uploaded.

This change is dependent on rust-lang/cargo#6453, which adds this
feature to the base `cargo publish` command.

The motivation behind this PR is the same as the above mentioned
cargo PR: reducing the amount of packaging errors that can happen
due to people not being able to verify their code because it has
some feature requirements for compilation, ultimately resulting in
a more healthy package ecosystem.
@spacekookie
Copy link
Contributor Author

spacekookie commented Jan 29, 2019

ping @sunng87: Hey there, apologies for the long wait!

I added the docs to README.md (I hope this is sufficient?) as well as resolving the merge conflict from master

@sunng87 sunng87 merged commit a3e8a3a into crate-ci:master Jan 29, 2019
@sunng87
Copy link
Collaborator

sunng87 commented Jan 29, 2019

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants