doc(yank): mention [email protected] and revoking creds

src/doc/man/cargo-yank.md

@@ -61,7 +61,16 @@ A common workflow is to yank a crate having already published a semver
 compatible version, to reduce the probability of preventing dependent
 crates from compiling.
 
+To address copyright, licensing, or personal data issues with your published
+crate, contact the maintainers of the registry you used. For crates.io, refer
+to their [policies] and contact them at <[email protected]>.
+
+If your credentials have been leaked, the recommended process is to revoke them
+immediately. Once a crate is published, it's impossible to know if those leaked
+credentials have been copied, so taking swift action is crucial.
+
 [RustSec]: https://rustsec.org/
+[policies]: https://crates.io/policies
 
 ## OPTIONS
 

src/doc/man/generated_txt/cargo-yank.txt

@@ -66,6 +66,16 @@ DESCRIPTION
        compatible version, to reduce the probability of preventing dependent
        crates from compiling.
 
+       To address copyright, licensing, or personal data issues with your
+       published crate, contact the maintainers of the registry you used. For
+       crates.io, refer to their policies <https://crates.io/policies> and
+       contact them at <[email protected]>.
+
+       If your credentials have been leaked, the recommended process is to
+       revoke them immediately. Once a crate is published, it’s impossible to
+       know if those leaked credentials have been copied, so taking swift
+       action is crucial.
+
 OPTIONS
    Yank Options
        --vers version, --version version

src/doc/src/commands/cargo-yank.md

@@ -61,7 +61,16 @@ A common workflow is to yank a crate having already published a semver
 compatible version, to reduce the probability of preventing dependent
 crates from compiling.
 
+To address copyright, licensing, or personal data issues with your published
+crate, contact the maintainers of the registry you used. For crates.io, refer
+to their [policies] and contact them at <[email protected]>.
+
+If your credentials have been leaked, the recommended process is to revoke them
+immediately. Once a crate is published, it's impossible to know if those leaked
+credentials have been copied, so taking swift action is crucial.
+
 [RustSec]: https://rustsec.org/
+[policies]: https://crates.io/policies
 
 ## OPTIONS
 

src/etc/man/cargo-yank.1

@@ -91,6 +91,14 @@ irrespective of susceptibility to the vulnerability in question.
 A common workflow is to yank a crate having already published a semver
 compatible version, to reduce the probability of preventing dependent
 crates from compiling.
+.sp
+To address copyright, licensing, or personal data issues with your published
+crate, contact the maintainers of the registry you used. For crates.io, refer
+to their \fIpolicies\fR <https://crates.io/policies> and contact them at <[email protected]>\&.
+.sp
+If your credentials have been leaked, the recommended process is to revoke them
+immediately. Once a crate is published, it\[cq]s impossible to know if those leaked
+credentials have been copied, so taking swift action is crucial.
 .SH "OPTIONS"
 .SS "Yank Options"
 .sp