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

Fix up kv feature activation #659

Merged
merged 2 commits into from
Jan 10, 2025
Merged

Fix up kv feature activation #659

merged 2 commits into from
Jan 10, 2025

Conversation

KodrAus
Copy link
Contributor

@KodrAus KodrAus commented Jan 10, 2025

Closes #658

Looks like a feature combination broke in 0.4.23, so I've added cargo hack to our CI to make sure we test all possible combinations.

@KodrAus KodrAus changed the title Use cargo hack in CI to test all feature combinations Fix up kv feature activation Jan 10, 2025
@@ -44,7 +44,7 @@ release_max_level_info = []
release_max_level_debug = []
release_max_level_trace = []

std = []
std = ["value-bag?/std"]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this supported in Rust 1.60 (our MSRV)?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://doc.rust-lang.org/cargo/reference/features.html

According to the doc linked, it's available starting from 1.60 so it should be fine.

Copy link
Contributor

@tisonkun tisonkun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing this. And sorry I don't catch this issue in my pr.

@@ -44,7 +44,7 @@ release_max_level_info = []
release_max_level_debug = []
release_max_level_trace = []

std = []
std = ["value-bag?/std"]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://doc.rust-lang.org/cargo/reference/features.html

According to the doc linked, it's available starting from 1.60 so it should be fine.

@KodrAus
Copy link
Contributor Author

KodrAus commented Jan 10, 2025

@tisonkun No problems! It's our fault for not catching it in CI. I've been meaning to add cargo-hack here for a while, it's a great way to test projects with lots of feature flags.

@KodrAus KodrAus merged commit 5fcb50e into master Jan 10, 2025
28 checks passed
@KodrAus KodrAus deleted the fix/feature-builds branch January 10, 2025 21:50
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.

0.4.23 causes build failures
3 participants