|
| 1 | +CARGO-REPORT-FUTURE-INCOMPATIBILITIES(1) |
| 2 | + |
| 3 | +NAME |
| 4 | + cargo-report-future-incompatibilities — Reports any crates which will |
| 5 | + eventually stop compiling |
| 6 | + |
| 7 | +SYNOPSIS |
| 8 | + cargo report future-incompatibilities [options] |
| 9 | + |
| 10 | +DESCRIPTION |
| 11 | + Displays a report of future-incompatible warnings that were emitted |
| 12 | + during previous builds. These are warnings for changes that may become |
| 13 | + hard errors in the future, causing dependencies to stop building in a |
| 14 | + future version of rustc. |
| 15 | + |
| 16 | + For more, see the chapter on Future incompat report |
| 17 | + <https://doc.rust-lang.org/cargo/reference/future-incompat-report.html>. |
| 18 | + |
| 19 | +OPTIONS |
| 20 | + --id id |
| 21 | + Show the report with the specified Cargo-generated id. If not |
| 22 | + specified, shows the most recent report. |
| 23 | + |
| 24 | + Package Selection |
| 25 | + By default, the package in the current working directory is selected. |
| 26 | + The -p flag can be used to choose a different package in a workspace. |
| 27 | + |
| 28 | + -p spec, --package spec |
| 29 | + The package to display a report for. See cargo-pkgid(1) for the SPEC |
| 30 | + format. |
| 31 | + |
| 32 | + Display Options |
| 33 | + -v, --verbose |
| 34 | + Use verbose output. May be specified twice for “very verbose” |
| 35 | + output which includes extra output such as dependency warnings and |
| 36 | + build script output. May also be specified with the term.verbose |
| 37 | + config value |
| 38 | + <https://doc.rust-lang.org/cargo/reference/config.html>. |
| 39 | + |
| 40 | + -q, --quiet |
| 41 | + Do not print cargo log messages. May also be specified with the |
| 42 | + term.quiet config value |
| 43 | + <https://doc.rust-lang.org/cargo/reference/config.html>. |
| 44 | + |
| 45 | + --color when |
| 46 | + Control when colored output is used. Valid values: |
| 47 | + |
| 48 | + o auto (default): Automatically detect if color support is |
| 49 | + available on the terminal. |
| 50 | + |
| 51 | + o always: Always display colors. |
| 52 | + |
| 53 | + o never: Never display colors. |
| 54 | + |
| 55 | + May also be specified with the term.color config value |
| 56 | + <https://doc.rust-lang.org/cargo/reference/config.html>. |
| 57 | + |
| 58 | + Manifest Options |
| 59 | + --locked |
| 60 | + Asserts that the exact same dependencies and versions are used as |
| 61 | + when the existing Cargo.lock file was originally generated. Cargo |
| 62 | + will exit with an error when either of the following scenarios |
| 63 | + arises: |
| 64 | + |
| 65 | + o The lock file is missing. |
| 66 | + |
| 67 | + o Cargo attempted to change the lock file due to a different |
| 68 | + dependency resolution. |
| 69 | + |
| 70 | + It may be used in environments where deterministic builds are |
| 71 | + desired, such as in CI pipelines. |
| 72 | + |
| 73 | + --offline |
| 74 | + Prevents Cargo from accessing the network for any reason. Without |
| 75 | + this flag, Cargo will stop with an error if it needs to access the |
| 76 | + network and the network is not available. With this flag, Cargo will |
| 77 | + attempt to proceed without the network if possible. |
| 78 | + |
| 79 | + Beware that this may result in different dependency resolution than |
| 80 | + online mode. Cargo will restrict itself to crates that are |
| 81 | + downloaded locally, even if there might be a newer version as |
| 82 | + indicated in the local copy of the index. See the cargo-fetch(1) |
| 83 | + command to download dependencies before going offline. |
| 84 | + |
| 85 | + May also be specified with the net.offline config value |
| 86 | + <https://doc.rust-lang.org/cargo/reference/config.html>. |
| 87 | + |
| 88 | + --frozen |
| 89 | + Equivalent to specifying both --locked and --offline. |
| 90 | + |
| 91 | + Common Options |
| 92 | + +toolchain |
| 93 | + If Cargo has been installed with rustup, and the first argument to |
| 94 | + cargo begins with +, it will be interpreted as a rustup toolchain |
| 95 | + name (such as +stable or +nightly). See the rustup documentation |
| 96 | + <https://rust-lang.github.io/rustup/overrides.html> for more |
| 97 | + information about how toolchain overrides work. |
| 98 | + |
| 99 | + --config KEY=VALUE or PATH |
| 100 | + Overrides a Cargo configuration value. The argument should be in |
| 101 | + TOML syntax of KEY=VALUE, or provided as a path to an extra |
| 102 | + configuration file. This flag may be specified multiple times. See |
| 103 | + the command-line overrides section |
| 104 | + <https://doc.rust-lang.org/cargo/reference/config.html#command-line-overrides> |
| 105 | + for more information. |
| 106 | + |
| 107 | + -C PATH |
| 108 | + Changes the current working directory before executing any specified |
| 109 | + operations. This affects things like where cargo looks by default |
| 110 | + for the project manifest (Cargo.toml), as well as the directories |
| 111 | + searched for discovering .cargo/config.toml, for example. This |
| 112 | + option must appear before the command name, for example cargo -C |
| 113 | + path/to/my-project build. |
| 114 | + |
| 115 | + This option is only available on the nightly channel |
| 116 | + <https://doc.rust-lang.org/book/appendix-07-nightly-rust.html> and |
| 117 | + requires the -Z unstable-options flag to enable (see #10098 |
| 118 | + <https://github.com/rust-lang/cargo/issues/10098>). |
| 119 | + |
| 120 | + -h, --help |
| 121 | + Prints help information. |
| 122 | + |
| 123 | + -Z flag |
| 124 | + Unstable (nightly-only) flags to Cargo. Run cargo -Z help for |
| 125 | + details. |
| 126 | + |
| 127 | +ENVIRONMENT |
| 128 | + See the reference |
| 129 | + <https://doc.rust-lang.org/cargo/reference/environment-variables.html> |
| 130 | + for details on environment variables that Cargo reads. |
| 131 | + |
| 132 | +EXIT STATUS |
| 133 | + o 0: Cargo succeeded. |
| 134 | + |
| 135 | + o 101: Cargo failed to complete. |
| 136 | + |
| 137 | +EXAMPLES |
| 138 | + 1. Display the latest future-incompat report: |
| 139 | + |
| 140 | + cargo report future-incompat |
| 141 | + |
| 142 | + 2. Display the latest future-incompat report for a specific package: |
| 143 | + |
| 144 | + cargo report future-incompat --package [email protected] |
| 145 | + |
| 146 | +SEE ALSO |
| 147 | + cargo(1), cargo-report(1), cargo-build(1) |
| 148 | + |
0 commit comments