Remove an excess newline

The udpate_message already has a newline when it is there. When it is an
empty string, it ends up adding an unnecessary blank line.
This commit is contained in:
Eric Huss 2025-03-21 16:28:57 -07:00
parent b17b9a4b90
commit 0b2299e889
2 changed files with 1 additions and 7 deletions

View File

@ -483,7 +483,7 @@ You may want to consider updating them to a newer version to see if the issue ha
" "
To solve this problem, you can try the following approaches: To solve this problem, you can try the following approaches:
{update_message} {update_message}\
- If the issue is not solved by updating the dependencies, a fix has to be - 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 implemented by those dependencies. You can help with that by notifying the
maintainers of this problem (e.g. by creating a bug report) or by proposing a maintainers of this problem (e.g. by creating a bug report) or by proposing a

View File

@ -149,7 +149,6 @@ fn incompat_in_dependency() {
[NOTE] [NOTE]
To solve this problem, you can try the following approaches: 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 - 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 implemented by those dependencies. You can help with that by notifying the
maintainers of this problem (e.g. by creating a bug report) or by proposing a maintainers of this problem (e.g. by creating a bug report) or by proposing a
@ -184,7 +183,6 @@ means and how to resolve it.
To solve this problem, you can try the following approaches: 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 - 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 implemented by those dependencies. You can help with that by notifying the
maintainers of this problem (e.g. by creating a bug report) or by proposing a maintainers of this problem (e.g. by creating a bug report) or by proposing a
@ -634,7 +632,6 @@ fix to the maintainers (e.g. by creating a pull request):
section in `Cargo.toml` to use your own version of the dependency. For more section in `Cargo.toml` to use your own version of the dependency. For more
information, see: information, see:
https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch-section https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch-section
[NOTE] this report can be shown with `cargo report future-incompatibilities --id 1` [NOTE] this report can be shown with `cargo report future-incompatibilities --id 1`
"#]].unordered()) "#]].unordered())
@ -662,7 +659,6 @@ You may want to consider updating them to a newer version to see if the issue ha
big_update v1.0.0 has the following newer versions available: 2.0.0 big_update v1.0.0 has the following newer versions available: 2.0.0
with_updates v1.0.0 has the following newer versions available: 1.0.1, 1.0.2, 3.0.1 with_updates v1.0.0 has the following newer versions available: 1.0.1, 1.0.2, 3.0.1
- If the issue is not solved by updating the dependencies, a fix has to be - 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 implemented by those dependencies. You can help with that by notifying the
maintainers of this problem (e.g. by creating a bug report) or by proposing a maintainers of this problem (e.g. by creating a bug report) or by proposing a
@ -724,7 +720,6 @@ fn correct_report_id_when_cached() {
[NOTE] [NOTE]
To solve this problem, you can try the following approaches: 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 - 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 implemented by those dependencies. You can help with that by notifying the
maintainers of this problem (e.g. by creating a bug report) or by proposing a maintainers of this problem (e.g. by creating a bug report) or by proposing a
@ -752,7 +747,6 @@ https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch
[NOTE] [NOTE]
To solve this problem, you can try the following approaches: 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 - 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 implemented by those dependencies. You can help with that by notifying the
maintainers of this problem (e.g. by creating a bug report) or by proposing a maintainers of this problem (e.g. by creating a bug report) or by proposing a