-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
feat: Stabilize MSRV-aware resolver config #14639
Conversation
Note: the final touches are not in place for this PR but I assume people can check their boxes based on the whole and assuming comments on this PR will get resolved. I propose that we stabilize the MSRV-aware resolver.
This includes stabilizing
This does not include stabilizing
Deviations from the RFC
I had considered proposing we have this cover
@rfcbot fcp merge |
Team member @epage has proposed to merge this. The next step is review by the rest of the tagged team members: No concerns currently listed. Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
☔ The latest upstream changes (presumably #14636) made this pull request unmergeable. Please resolve the merge conflicts. |
This includes - `cargo generate-lockfile --ignore-rust-version` - `cargo update --ignore-rust-version` This does not include - `edition = "2024"` - `resolver = "3"`
32bf8d2
to
ea2f0d2
Compare
ea2f0d2
to
d4bdbc4
Compare
🔔 This is now entering its final comment period, as per the review above. 🔔 |
src/doc/src/reference/unstable.md
Outdated
- `--ignore-rust-version` CLI option | ||
- Setting the dependency's version requirement higher than any version with a compatible `rust-version` | ||
- Specifying the version to `cargo update` with `--precise` | ||
This was stabilized in 1.83 in #. |
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.
This was stabilized in 1.83 in #. | |
This was stabilized in 1.83 in [#14639](https://github.com/rust-lang/cargo/pull/14639). |
BTW, do you plan not to move anything to "Stabilized" section until every feature is implemented? Should we move just these two stabilized feature under independent h2 headings, which won't break link validity?
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.
Hadn't really thought that through. Its a question of whether the stable section is documenting features or flags. Overall, I don't have a strong preference.
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 slightly towards moving them, but not going to block this PR for that reason.
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.
As its already that way for some parts, let's handle the decision separately
d4bdbc4
to
15f149e
Compare
cdb8304
to
68d86fc
Compare
The final comment period, with a disposition to merge, as per the review above, is now complete. As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed. This will be merged soon. |
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.
Some nitpicks as a reader that often forgot what I was reading in previous paragraphs.
68d86fc
to
f3c74e7
Compare
f3c74e7
to
498d4df
Compare
@bors r+ The FCP has ended. To maximise the testing window I am going to merge this soon. Thank you all for your inputs! |
☀️ Test successful - checks-actions |
Update cargo 7 commits in 8c30ce53688e25f7e9d860b33cc914fb2957ca9a..cf53cc54bb593b5ec3dc2be4b1702f50c36d24d5 2024-10-15 16:43:16 +0000 to 2024-10-18 13:56:15 +0000 - feat: Stabilize MSRV-aware resolver config (rust-lang/cargo#14639) - Help with `[patch.crates.io]` (rust-lang/cargo#14700) - test: Migrate publish snapshotting to snapbox (rust-lang/cargo#14642) - Bump to 0.85.0; update changelog (rust-lang/cargo#14695) - Fix typo in faq.md (rust-lang/cargo#14696) - fix(registry): `HttpRegistry` `block_until_ready` returns early when work is still pending (rust-lang/cargo#14694) - fix(resolver): avoid cloning when iterating using RcVecIter (rust-lang/cargo#14690)
docs(ci): Don't constrainty latest_deps job by MSRV Missed this in #14639
Missed this in rust-lang#14639
test: Remove unused msrv-policy ### What does this PR try to resolve? Missed this in #14639 ### How should we test and review this PR? ### Additional information
What does this PR try to resolve?
This includes
cargo generate-lockfile --ignore-rust-version
cargo update --ignore-rust-version
This does not include
edition = "2024"
resolver = "3"
This is part of #9930
How should we test and review this PR?
Additional information
This is stacked on top of #14636. The commits for this PR start with the commit with a title that matches the PR title.
FCP