itsscb/cargo
1
0
Fork 0
mirror of https://github.com/rust-lang/cargo.git synced 2025-09-25 11:14:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(future): Remove leading newline to match note conventions

Browse Source
This commit is contained in:
Ed Page 2025-09-08 15:05:16 -05:00
parent 8682394e7b
commit 1b9265ca73
2 changed files with 5 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
src/cargo/core/compiler/future_incompat.rs
View File

@ -496,12 +496,7 @@ https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch
String::new()
} else {
let mut suggestion_message = String::new();
writeln!(
&mut suggestion_message,
"
{suggestion_header}"
)
.unwrap();
writeln!(&mut suggestion_message, "{suggestion_header}").unwrap();
for suggestion in &suggestions {
writeln!(
&mut suggestion_message,

14
tests/testsuite/future_incompat_report.rs
View File

@ -146,8 +146,7 @@ fn incompat_in_dependency() {
.with_stderr_data(str![[r#"
[FINISHED] `dev` profile [unoptimized + debuginfo] target(s) in [ELAPSED]s
[WARNING] the following packages contain code that will be rejected by a future version of Rust: bar v1.0.0
[NOTE]
To solve this problem, you can try the following approaches:
[NOTE] To solve this problem, you can try the following approaches:
- If the issue is not solved by updating the dependencies, a fix has to be
implemented by those dependencies. You can help with that by notifying the
@ -180,7 +179,6 @@ to be in wide use.
Each warning should contain a link for more information on what the warning
means and how to resolve it.
To solve this problem, you can try the following approaches:
- If the issue is not solved by updating the dependencies, a fix has to be
@ -603,8 +601,7 @@ fn suggestions_for_updates() {
[CHECKING] foo v0.1.0 ([ROOT]/foo)
[FINISHED] `dev` profile [unoptimized + debuginfo] target(s) in [ELAPSED]s
[WARNING] the following packages contain code that will be rejected by a future version of Rust: big_update v1.0.0, with_updates v1.0.0, without_updates v1.0.0
[NOTE]
To solve this problem, you can try the following approaches:
[NOTE] To solve this problem, you can try the following approaches:
- Some affected dependencies have newer versions available.
You may want to consider updating them to a newer version to see if the issue has been fixed.
@ -651,7 +648,6 @@ to be in wide use.
Each warning should contain a link for more information on what the warning
means and how to resolve it.
To solve this problem, you can try the following approaches:
- Some affected dependencies have newer versions available.
@ -718,8 +714,7 @@ fn correct_report_id_when_cached() {
[CHECKING] foo v1.0.0 ([ROOT]/foo)
[FINISHED] `dev` profile [unoptimized + debuginfo] target(s) in [ELAPSED]s
[WARNING] the following packages contain code that will be rejected by a future version of Rust: bar v1.0.0
[NOTE]
To solve this problem, you can try the following approaches:
[NOTE] To solve this problem, you can try the following approaches:
- If the issue is not solved by updating the dependencies, a fix has to be
implemented by those dependencies. You can help with that by notifying the
@ -745,8 +740,7 @@ https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch
.with_stderr_data(str![[r#"
[FINISHED] `dev` profile [unoptimized + debuginfo] target(s) in [ELAPSED]s
[WARNING] the following packages contain code that will be rejected by a future version of Rust: bar v1.0.0
[NOTE]
To solve this problem, you can try the following approaches:
[NOTE] To solve this problem, you can try the following approaches:
- If the issue is not solved by updating the dependencies, a fix has to be
implemented by those dependencies. You can help with that by notifying the