-
Notifications
You must be signed in to change notification settings - Fork 136
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
subprotocol
crates no_std
support
#1315
Conversation
Bencher Report
Click to view all benchmark results
|
Bencher Report
Click to view all benchmark results
|
Bencher Report
Click to view all benchmark results
|
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.
hey @Georges760 thanks for this
let's try to merge this PR before releasing v1.2.0
bumping MAJOR makes total sense
however some of the PATCH bumps are redundant since they've already been covered via #1300 in preparation for the release v1.2.0, so it would be redundant to bump 2x before publishing the crates to crates.io
we should rebase the PR to avoid bumping PATCH 2x on crates that have already been bumped via #1300, namely:
roles_logic_sv2
sv2_ffi
we should also squash a60cbcc for a cleaner commit history
publishing with all-features is overengineering: - no_std is being dropped via stratum-mining#1315 - with_serde will be dropped soon - no point in publishing docs for code under prop_test
publishing with all-features is overengineering: - no_std is being dropped via stratum-mining#1315 - with_serde will be dropped soon
publishing with all-features is overengineering: - no_std is being dropped via stratum-mining#1315 - with_serde will be dropped soon
publishing with all-features is overengineering: - no_std is being dropped via stratum-mining#1315 - with_serde will be dropped soon - no point in publishing docs for code under prop_test
publishing with all-features is overengineering: - no_std is being dropped via stratum-mining#1315 - with_serde will be dropped soon - no point in publishing docs for code under prop_test
publishing with all-features is overengineering: - no_std is being dropped via stratum-mining#1315 - with_serde will be dropped soon - it is sufficient to publish the docs with with_buffer_pool feature flag
publishing with all-features is overengineering: - no_std is being deprecated via stratum-mining#1315 - with_serde will be deprecated soon - no point in publishing docs for code under prop_test
publishing with all-features is overengineering: - no_std is being deprecated via stratum-mining#1315 - with_serde will be deprecated soon
publishing with all-features is overengineering: - no_std is being deprecated via stratum-mining#1315 - with_serde will be deprecated soon
publishing with all-features is overengineering: - no_std is being deprecated via stratum-mining#1315 - with_serde will be deprecated soon - no point in publishing docs for code under prop_test
publishing with all-features is overengineering: - no_std is being deprecated via stratum-mining#1315 - with_serde will be deprecated soon - no point in publishing docs for code under prop_test or disable_nopanic
publishing with all-features is overengineering: - no_std is being deprecated via stratum-mining#1315 - with_serde will be deprecated soon - it is sufficient to publish the docs with noise_sv2 and with_buffer_pool feature flags
…stribution_sv2`: remove the `no_std` feature and make them `#![no_std]` as they never use `std` anywhere. - bump their MAJOR version because of feature removal - bump the dependant crates PATCH version - updates docs
a60cbcc
to
e7f152d
Compare
@plebhash done |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1315 +/- ##
=======================================
Coverage 19.29% 19.29%
=======================================
Files 164 164
Lines 10852 10852
=======================================
Hits 2094 2094
Misses 8758 8758
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
common_messages_sv2
job_declaration_sv2
mining_sv2
template_distribution_sv2
: remove theno_std
feature and make them#![no_std]
as they never usestd
anywhere.