@@ -3,8 +3,7 @@ release.hs
33
44This tool automates some aspects of releasing a new version of Stack. It
55currently handles some tasks that need to be performed on each platform:
6- building the release, running some pre-release checks, and uploading binaries to
7- a Github release.
6+ building the release, running integration tests, and other pre-release checks.
87
98See [ Checklist] ( ../../doc/maintainers/releases.md )  of
109additional manual release steps.
@@ -17,23 +16,6 @@ These must be installed in the PATH to use the release tool:
1716-  stack
1817-  git (for Windows, [ msysgit] ( https://msysgit.github.io )  is recommended).
1918
20- To create a signed binary package, you need:
21- 
22- -  GPG installed and in the PATH (included with
23-   [ msysgit] ( https://msysgit.github.io )  on Windows)
24- -  ` [email protected] `  secret key in GPG keyring. You may also use the
25-   environment variable ` STACK_RELEASE_GPG_KEY ` , which should be
26-   set to the hexadecimal (0xLONG) identifier of the GPG key.
27- 
28- To upload a binary to a Github release, you also need:
29- 
30- -  A [ Github authorization token] ( https://github.com/settings/tokens )  with
31-   ` public_repo `  scope.
32- -  Set ` GITHUB_AUTH_TOKEN `  environment variable to the authorization token.
33- -  A [ Github release] ( https://github.com/commercialhaskell/stack/releases ) 
34-   (probably as a draft) with a tag for the stack package's version (e.g.
35-   ` vX.Y.Z ` ).
36- 
3719Invocation
3820---------- 
3921
@@ -46,28 +28,13 @@ The tool must be run in the root of the working tree.
4628The release tool is shake-based, so all standard shake options apply. In
4729addition, the following options are accepted:
4830
49- *  ` --gpg-key ` : override GPG key used to sign the distribution packages. By
50-   default the 
` [email protected] `  key is used.
51- *  ` --github-auth-token ` : override the Github authorization token.
52- *  ` --github-release-tag ` : overrides the Github Release tag that binaries are
5331*  ` --allow-dirty ` : by default, the ` check `  rule aborts if the working tree is
5432  dirty, but this will allow it to continue.
5533  uploaded to.
5634
57- You may also use the following environment variables in order to use a custom
58- GPG key:
59- *  ` STACK_RELEASE_GPG_KEY `  should be set to the hexadecimal identifier (0xLONG) of the
60-   GPG key
61- 
6235### Targets  
6336
64- *  ` release ` : check, build,  and upload .
37+ *  ` release ` : check  and build .
6538*  ` check ` : run pre-release checks.
6639*  ` build ` : build and sign the binary distribution.
67- *  ` upload ` : upload the binary distribution to the Github release.
68- *  ` build-<distro>-<ver> ` : build package for Linux distribution.
69- *  ` upload-<distro>-<ver> ` : upload package for Linux distribution to private package repository.
7040*  ` clean ` : delete the build artifacts.
71- 
72- ` <distro> `  can have one of these values: ` ubuntu ` , ` debian ` , ` centos ` , ` fedora ` .  
73- ` <ver> `  is the version of the distribution (e.g., ` 14.04 `  for Ubuntu).
0 commit comments