diff options
| author | John J. Camilleri <john@digitalgrammars.com> | 2021-08-09 13:41:25 +0200 |
|---|---|---|
| committer | John J. Camilleri <john@digitalgrammars.com> | 2021-08-09 13:41:25 +0200 |
| commit | 723bec1ba0579ace280f6d67ad71a1596fc4f166 (patch) | |
| tree | bb8763c6111e93a3df5ac6847bb9435dce5e934f /RELEASE.md | |
| parent | 265f08d6eec62e1f30a2a1f6fbc3bc18be17948e (diff) | |
Changes made in order to get Hackage upload working
Diffstat (limited to 'RELEASE.md')
| -rw-r--r-- | RELEASE.md | 11 |
1 files changed, 7 insertions, 4 deletions
diff --git a/RELEASE.md b/RELEASE.md index 04bd4b933..1deaa3a90 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -47,11 +47,14 @@ but the generated _artifacts_ must be manually attached to the release as _asset In order to do this you will need to be added the [GF maintainers](https://hackage.haskell.org/package/gf/maintainers/) on Hackage. -1. Run `make sdist` +1. Run `stack sdist --test-tarball` and address any issues. 2. Upload the package, either: - 1. **Manually**: visit <https://hackage.haskell.org/upload> and upload the file `dist/gf-X.Y.tar.gz` - 2. **via Cabal (≥2.4)**: `cabal upload dist/gf-X.Y.tar.gz` -3. If the documentation-building fails on the Hackage server, do: + 1. **Manually**: visit <https://hackage.haskell.org/upload> and upload the file generated by the previous command. + 2. **via Stack**: `stack upload . --candidate` +3. After testing the candidate, publish it: + 1. **Manually**: visit <https://hackage.haskell.org/package/gf-X.Y.Z/candidate/publish> + 1. **via Stack**: `stack upload .` +4. If the documentation-building fails on the Hackage server, do: ``` cabal v2-haddock --builddir=dist/docs --haddock-for-hackage --enable-doc cabal upload --documentation dist/docs/*-docs.tar.gz |