stack upload command¶
Hackage accepts packages for uploading in a standard form, a compressed archive
('tarball') in the format produced by Cabal's
stack upload generates a file for your package, in the format accepted by
Hackage for uploads, and uploads the package to Hackage. For example, if the
current working directory is the root directory of your project:
HACKAGE_PASSWORD environment variables¶
stack upload will request a Hackage username and password to authenticate.
This can be avoided by setting the
environment variables. For
HACKAGE_KEY environment variable¶
Hackage allows its members to register an API authentification token and to authenticate using the token.
A Hackage API authentification token can be used with
stack upload instead of
username and password, by setting the
HACKAGE_KEY environment variable. For
Pass the flag to upload a package candidate.
Pass the flag to disable checks of the package for common mistakes. By default, the command will check the package for common mistakes.
--pvp-bounds <pvp_bounds_mode> option determines whether and, if so, how
PVP version bounds should be added to the Cabal file of the package. The
available modes for basic use are:
available modes for use with Cabal file revisions are
For futher information, see the YAML configuration documentation.
--tar-dir <path_to_directory> option determines whether the package
archive should be copied to the specified directory.
Set the flag to cause Stack to test the resulting package archive, by attempting to build it.