-
Notifications
You must be signed in to change notification settings - Fork 140
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
use cargo semver-checks
v0.37 and bump crate versions as a follow-up to #1276
#1300
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1300 +/- ##
=======================================
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. |
Bencher Report
Click to view all benchmark results
|
plebhash
force-pushed
the
semver-checks-37
branch
from
December 16, 2024 12:15
491045b
to
e00b513
Compare
Bencher Report
Click to view all benchmark results
|
Bencher Report
🚨 4 Alerts
Click to view all benchmark results
|
GitGab19
reviewed
Dec 16, 2024
plebhash
force-pushed
the
semver-checks-37
branch
4 times, most recently
from
December 17, 2024 09:37
03312c2
to
0d6e7f3
Compare
GitGab19
reviewed
Dec 17, 2024
plebhash
force-pushed
the
semver-checks-37
branch
2 times, most recently
from
December 17, 2024 12:18
9a05fc5
to
5d68ca6
Compare
GitGab19
approved these changes
Dec 17, 2024
since v37, cargo semver-checks enforces that removal of features are breaking changes therefore we need to update serde_v2 as a follow up to stratum-mining#1230
since we bumpbed serde_sv2 to 2.0.0
since we bumpted serde_sv2 to 2.0.0
since we bumped serde_sv2 and binary_sv2
since v37, cargo semver-checks enforces that removal of features are breaking changes therefore we need to update serde_v2 as a follow up to stratum-mining#1230
since we bumpbed const_sv2 to 3.0.0
since we bumpbed const_sv2 to 3.0.0
since we bumpbed const_sv2 to 3.0.0
since we bumpbed const_sv2 to 3.0.0
since we bumpbed const_sv2 to 3.0.0
since we bumpbed const_sv2 to 3.0.0
since v37, cargo semver-checks enforces that removal of features are breaking changes therefore we need to update framing_v2 as a follow up to stratum-mining#1230
since we bumped framing_sv2 to 3.0.0
crate version has already been bumped before release. no need to bump again
plebhash
force-pushed
the
semver-checks-37
branch
from
December 18, 2024 03:20
5d68ca6
to
a4f8c43
Compare
plebhash
added a commit
to plebhash/stratum
that referenced
this pull request
Dec 18, 2024
as a follow up to stratum-mining#1230 and stratum-mining#1300
This was referenced Dec 18, 2024
Merged
plebhash
added a commit
to plebhash/stratum
that referenced
this pull request
Dec 18, 2024
as a follow up to stratum-mining#1230 and stratum-mining#1300
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
follow up to #1276 according to this comment: #1275 (comment)
rationale
we are planning to remove more cargo build features in the future, and therefore it's desirable to enforce semver around this via CI
as a consequence, we need to use
cargo semver-check
v0.37 (or greater, but always locked)this creates incompatibilities with MSRV, therefore we need to run
cargo semver-check
onstable
finally, switching
cargo semver-check
to v0.37 forced us to bump many crate versionsPR changes:
cargo semver-check
v0.37stable
toolchain instead of MSRV 1.75no_std
features on lock version for cargo semver-checks #1276