-
Notifications
You must be signed in to change notification settings - Fork 127
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 rust stable for semver CI #1104
Conversation
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.
ACK
Bencher
🚨 1 ALERT: Threshold Boundary Limit exceeded!
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
🚨 1 ALERT: Threshold Boundary Limit exceeded!
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
🚨 8 ALERTS: Threshold Boundary Limits exceeded!
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
I strongly suggest to NOT change MSRV as we want, otherwise having an MSRV is not of any utility. For example here we change it ONLY for support something that we need on dev/release env no reason to bump MSRV for it, we can just use the right version when we run semver check. Our libraries do not need 1.77 they can work with 1.75 without any issue. So we should change MSRV only if we really need to use some feature added by a new rust version, or MAYBE (?) better we can define MSRV as the last n version so it get "automatically" increased. |
please see #1110 |
This PR did not change MSRV, it changed just the version installed in the CI to run |
Not sure from branch name and form description I supposed the pr goal was changing MSRV but if is not so diregard my comment |
cargo semver-checks
had a new release a couple hours ago: https://github.com/obi1kenobi/cargo-semver-checks/releases/tag/v0.34.0this release changed MSRV of
cargo semver-checks
from1.75
to1.77
currently,
semver-check.yaml
is installing1.75
:stratum/.github/workflows/semver-check.yaml
Lines 21 to 25 in a090844
as a consequence, our entire SemVer CI is failing with:
example
this PR changes
1.75
tostable
onsemver-check.yaml
, so that we don't face this issue again in the future