-
Notifications
You must be signed in to change notification settings - Fork 141
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
remove serde feature from protocol crate #1455
remove serde feature from protocol crate #1455
Conversation
bec0425
to
b39cc2f
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1455 +/- ##
==========================================
- Coverage 19.44% 19.34% -0.10%
==========================================
Files 146 144 -2
Lines 10244 10963 +719
==========================================
+ Hits 1992 2121 +129
- Misses 8252 8842 +590 Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
do we really need to delete the entire example?
isn't there a way to keep it, just not using serde
?
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.
writing this example was an outcome of the documentation effort
it would be a pity to lose it just because of the serde
deprecation, as it is still valuable
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.
I am writing an example without the serde flag..
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.
Done in: 32cbab3
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.
thanks, but please note that this should have been fixed on the original commit that erased the file, not adding a new commit to re-add the file
doing this way effectively erases the git history of the original file
I'm rebasing the branch to fix it
looks like we're going to have to bump MAJOR for all the crates where the https://github.com/stratum-mining/stratum/actions/runs/13152202385/job/36701547815?pr=1455 edit: actually, not necessarily ALL some have already bumped MAJOR (before being published, e.g.: |
6a79345
to
2b89e2c
Compare
2b89e2c
to
189d72a
Compare
189d72a
to
32cbab3
Compare
7133582
to
f9e4135
Compare
f9e4135
to
f7b068a
Compare
Part of: #1387