-
Notifications
You must be signed in to change notification settings - Fork 459
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
Minimum rustc version bumped in patch version #240
Comments
The rules around semver and "minimum supported rustc" are squishy at best, but the policy I personally use is at least 2 versions back from the current stable and otherwise updates can happen whenever. Are you unable to update rustc for other reasons though? |
No, I'm the author of a library which depends on Now, speaking as the author of a (different) crate going through the lib blitz, it would be nice if this were standardized, since minimum rustc versions are viral. I'm going to file an issue with the api-guidelines repository accordingly. |
Ok, in the case that it's not actively causing problems I'm going to go ahead and close this. This issue has come up many many times historically and we've never come up with a good guideline that's practical, but it's worth having a tracking issue! |
We also just noticed this. What was the rationale for suddenly bumping MSRC from 1.16.0 to 1.31.0?? We're using What's worst is that it seems like the bump was just made for using the
|
There's an excellent comment explaining MSRV and maintainers here, I'd recommend reading over that personally. I've decided to use the 2018 edition in this crate, so the minimum version is now 1.31.0. |
Hi, the minimum supported
rustc
version was bumped in a patch version. This is disruptive to downstream crates which have their own minimum supportedrustc
version, and which depend ongcc
using a Cargo.toml directive likegcc = "0.3"
. Unless I'm misinterpreting the Cargo SemVer rules, it would be ideal if you could yank the affected versions.The text was updated successfully, but these errors were encountered: