blob: e6250e976b51301606d2e4fb5fcd4ccdbb7bf811 [file] [log] [blame]
Jeff Vander Stoep956d1432020-09-18 13:46:24 +02001'\" t
2.\" Title: cargo-yank
3.\" Author: [see the "AUTHOR(S)" section]
4.\" Generator: Asciidoctor 2.0.10
5.\" Date: 2020-06-25
6.\" Manual: \ \&
7.\" Source: \ \&
8.\" Language: English
9.\"
10.TH "CARGO\-YANK" "1" "2020-06-25" "\ \&" "\ \&"
11.ie \n(.g .ds Aq \(aq
12.el .ds Aq '
13.ss \n[.ss] 0
14.nh
15.ad l
16.de URL
17\fI\\$2\fP <\\$1>\\$3
18..
19.als MTO URL
20.if \n[.g] \{\
21. mso www.tmac
22. am URL
23. ad l
24. .
25. am MTO
26. ad l
27. .
28. LINKSTYLE blue R < >
29.\}
30.SH "NAME"
31cargo\-yank \- Remove a pushed crate from the index
32.SH "SYNOPSIS"
33.sp
34\fBcargo yank [\fIOPTIONS\fP] \-\-vers \fIVERSION\fP [\fICRATE\fP]\fP
35.SH "DESCRIPTION"
36.sp
37The yank command removes a previously published crate\(cqs version from the
38server\(cqs index. This command does not delete any data, and the crate will
39still be available for download via the registry\(cqs download link.
40.sp
41Note that existing crates locked to a yanked version will still be able to
42download the yanked version to use it. Cargo will, however, not allow any new
43crates to be locked to any yanked version.
44.sp
45This command requires you to be authenticated with either the \fB\-\-token\fP option
46or using \fBcargo\-login\fP(1).
47.sp
48If the crate name is not specified, it will use the package name from the
49current directory.
50.SH "OPTIONS"
51.SS "Yank Options"
52.sp
53\fB\-\-vers\fP \fIVERSION\fP
54.RS 4
55The version to yank or un\-yank.
56.RE
57.sp
58\fB\-\-undo\fP
59.RS 4
60Undo a yank, putting a version back into the index.
61.RE
62.sp
63\fB\-\-token\fP \fITOKEN\fP
64.RS 4
65API token to use when authenticating. This overrides the token stored in
66the credentials file (which is created by \fBcargo\-login\fP(1)).
67.sp
68.URL "https://doc.rust\-lang.org/cargo/reference/config.html" "Cargo config" " "
69environment variables can be
70used to override the tokens stored in the credentials file. The token for
71crates.io may be specified with the \fBCARGO_REGISTRY_TOKEN\fP environment
72variable. Tokens for other registries may be specified with environment
73variables of the form \fBCARGO_REGISTRIES_NAME_TOKEN\fP where \fBNAME\fP is the name
74of the registry in all capital letters.
75.RE
76.sp
77\fB\-\-index\fP \fIINDEX\fP
78.RS 4
79The URL of the registry index to use.
80.RE
81.sp
82\fB\-\-registry\fP \fIREGISTRY\fP
83.RS 4
84Name of the registry to use. Registry names are defined in \c
85.URL "https://doc.rust\-lang.org/cargo/reference/config.html" "Cargo config files" "."
86If not specified, the default registry is used, which is defined by the
87\fBregistry.default\fP config key which defaults to \fBcrates\-io\fP.
88.RE
89.SS "Display Options"
90.sp
91\fB\-v\fP, \fB\-\-verbose\fP
92.RS 4
93Use verbose output. May be specified twice for "very verbose" output which
94includes extra output such as dependency warnings and build script output.
95May also be specified with the \fBterm.verbose\fP
96.URL "https://doc.rust\-lang.org/cargo/reference/config.html" "config value" "."
97.RE
98.sp
99\fB\-q\fP, \fB\-\-quiet\fP
100.RS 4
101No output printed to stdout.
102.RE
103.sp
104\fB\-\-color\fP \fIWHEN\fP
105.RS 4
106Control when colored output is used. Valid values:
107.sp
108.RS 4
109.ie n \{\
110\h'-04'\(bu\h'+03'\c
111.\}
112.el \{\
113. sp -1
114. IP \(bu 2.3
115.\}
116\fBauto\fP (default): Automatically detect if color support is available on the
117terminal.
118.RE
119.sp
120.RS 4
121.ie n \{\
122\h'-04'\(bu\h'+03'\c
123.\}
124.el \{\
125. sp -1
126. IP \(bu 2.3
127.\}
128\fBalways\fP: Always display colors.
129.RE
130.sp
131.RS 4
132.ie n \{\
133\h'-04'\(bu\h'+03'\c
134.\}
135.el \{\
136. sp -1
137. IP \(bu 2.3
138.\}
139\fBnever\fP: Never display colors.
140.RE
141.sp
142May also be specified with the \fBterm.color\fP
143.URL "https://doc.rust\-lang.org/cargo/reference/config.html" "config value" "."
144.RE
145.SS "Common Options"
146.sp
147\fB+TOOLCHAIN\fP
148.RS 4
149If Cargo has been installed with rustup, and the first argument to \fBcargo\fP
150begins with \fB+\fP, it will be interpreted as a rustup toolchain name (such
151as \fB+stable\fP or \fB+nightly\fP).
152See the \c
153.URL "https://github.com/rust\-lang/rustup/" "rustup documentation"
154for more information about how toolchain overrides work.
155.RE
156.sp
157\fB\-h\fP, \fB\-\-help\fP
158.RS 4
159Prints help information.
160.RE
161.sp
162\fB\-Z\fP \fIFLAG\fP...
163.RS 4
164Unstable (nightly\-only) flags to Cargo. Run \fBcargo \-Z help\fP for
165details.
166.RE
167.SH "ENVIRONMENT"
168.sp
169See \c
170.URL "https://doc.rust\-lang.org/cargo/reference/environment\-variables.html" "the reference" " "
171for
172details on environment variables that Cargo reads.
173.SH "EXIT STATUS"
174.sp
1750
176.RS 4
177Cargo succeeded.
178.RE
179.sp
180101
181.RS 4
182Cargo failed to complete.
183.RE
184.SH "EXAMPLES"
185.sp
186.RS 4
187.ie n \{\
188\h'-04' 1.\h'+01'\c
189.\}
190.el \{\
191. sp -1
192. IP " 1." 4.2
193.\}
194Yank a crate from the index:
195.sp
196.if n .RS 4
197.nf
198cargo yank \-\-vers 1.0.7 foo
199.fi
200.if n .RE
201.RE
202.SH "SEE ALSO"
203.sp
204\fBcargo\fP(1), \fBcargo\-login\fP(1), \fBcargo\-publish\fP(1)