1.4 KiB
RELEASING
-
Update version in
ghcup.cabal
andboostrap-haskell
(ghver
variable at the top of the script) -
Update
GHCup.Version
module.ghcupURL
must only be updated if we change theGHCupInfo
type or the YAML representation of it. The version of the YAML represents the change increments.ghcUpVer
is the current application version, read fromghcup.cabal
. -
Add ChangeLog entry
-
Add/fix downloads in
ghcup-<ver>.yaml
(underdata/metadata
), then verify withghcup-gen check -f ghcup-<ver>.yaml
and possibly (example only)ghcup-gen check-tarballs -f ghcup-<ver>.yaml -u 'ghc-8.10.7'
. Generally, new GHC/cabal/stack/hls versions are only added to the latest yaml file. New GHCup versions are added to all (great care must be taken here to not break the parser... e.g. ARM platforms don't parse in all older formats). -
Commit and git push with tag. Wait for tests to succeed and release artifacts to build.
-
Download release artifacts and upload them
downloads.haskell.org/ghcup
along with checksum files (sha256sum --tag * > SHA256SUMS && gpg --detach-sign -u <your-email> SHA256SUMS
) -
Add ghcup release artifacts to ALL yaml files (see point 4.)
-
Upload the final
ghcup-<ver>.yaml
towebhost.haskell.org/ghcup/data/
. -
Update
bootstrap-haskell
andbootstrap-haskell.ps1
towebhost.haskell.org/ghcup/sh/
-
Update the ghcup symlinks at
downloads.haskell.org/ghcup