@@ -94,7 +94,6 @@ Each new feature described below should explain how to use it.
94
94
* [ Build-plan] ( #build-plan ) — Emits JSON information on which commands will be run.
95
95
* [ timings] ( #timings ) — Generates a report on how long individual dependencies took to run.
96
96
* [ unit-graph] ( #unit-graph ) — Emits JSON for Cargo's internal graph structure.
97
- * [ future incompat report] ( #future-incompat-report ) — Displays a report for future incompatibilities that may error in the future.
98
97
* [ ` cargo rustc --print ` ] ( #rustc---print ) — Calls rustc with ` --print ` to display information from rustc.
99
98
* Configuration
100
99
* [ config-cli] ( #config-cli ) — Adds the ability to pass configuration options on the command-line.
@@ -1143,35 +1142,6 @@ cargo logout -Z credential-process
1143
1142
[ crates.io ] : https://crates.io/
1144
1143
[ config file ] : config.md
1145
1144
1146
- ### future incompat report
1147
- * RFC: [ #2834 ] ( https://github.com/rust-lang/rfcs/blob/master/text/2834-cargo-report-future-incompat.md )
1148
- * rustc Tracking Issue: [ #71249 ] ( https://github.com/rust-lang/rust/issues/71249 )
1149
-
1150
- The ` -Z future-incompat-report ` flag causes Cargo to check for
1151
- future-incompatible warnings in all dependencies. These are warnings for
1152
- changes that may become hard errors in the future, causing the dependency to
1153
- stop building in a future version of rustc. If any warnings are found, a small
1154
- notice is displayed indicating that the warnings were found, and provides
1155
- instructions on how to display a full report.
1156
-
1157
- A full report can be displayed with the `cargo report future-incompatibilities
1158
- -Z future-incompat-report --id ID` command, or by running the build again with
1159
- the ` --future-incompat-report ` flag. The developer should then update their
1160
- dependencies to a version where the issue is fixed, or work with the
1161
- developers of the dependencies to help resolve the issue.
1162
-
1163
- This feature can be configured through a ` [future-incompat-report] `
1164
- section in ` .cargo/config ` . Currently, the supported options are:
1165
-
1166
- ```
1167
- [future-incompat-report]
1168
- frequency = FREQUENCY
1169
- ```
1170
-
1171
- The supported values for ` FREQUENCY ` are 'always` and 'never', which control
1172
- whether or not a message is printed out at the end of ` cargo build ` / ` cargo check ` .
1173
-
1174
-
1175
1145
### ` cargo config `
1176
1146
1177
1147
* Original Issue: [ #2362 ] ( https://github.com/rust-lang/cargo/issues/2362 )
@@ -1403,6 +1373,11 @@ See [`cargo fix --edition`](../commands/cargo-fix.md) and [The Edition Guide](..
1403
1373
Custom named profiles have been stabilized in the 1.57 release. See the
1404
1374
[ profiles chapter] ( profiles.md#custom-profiles ) for more information.
1405
1375
1376
+ ### Future incompat report
1377
+
1378
+ Support for generating a future-incompat report has been stabilized
1379
+ in the 1.59 release. See the [ future incompat report chapter] ( future-incompat-report.md )
1380
+ for more information.
1406
1381
1407
1382
### scrape-examples
1408
1383
0 commit comments