Fix commercialhaskell#6618 Move Stack to GHC 9.6.6

Author: mpilgrem

.devcontainer/devcontainer.json

@@ -3,8 +3,8 @@
   "build": {
     "dockerfile": "GHC.Dockerfile",
     "args": {
-      "GHC_VERSION": "9.6.5",
-      "HLS_VERSION": "2.9.0.0",
+      "GHC_VERSION": "9.6.6",
+      "HLS_VERSION": "2.9.0.1",
       "USE_ZSH_FOR_ROOT": "unset-to-use-ash",
       "SET_LANG": "C.UTF-8",
       "SET_TZ": ""

CONTRIBUTING.md

@@ -342,8 +342,8 @@ Stack aims to depend on well-known packages. The specific versions on which it
 depends at any time are specified by `package.yaml` and `stack.yaml`. It does
 not aim to be compatible with more than one version of the `Cabal` package at
 any time. At the time of writing (May 2024) the package versions are primarily
-ones in Stackage snapshot LTS Haskell 22.21 (for GHC 9.6.5), together with
-extra-deps to depend on the latest version of `pantry` and `tar`.
+ones in Stackage snapshot LTS Haskell 22.28 (for GHC 9.6.6), together with
+extra-deps to depend on the latest version of `hpack`, `pantry` and `tar`.
 
 A Stack executable makes use of Cabal (the library) through a small 'Setup'
 executable that it compiles from Haskell source code. The executable compiles
@@ -663,7 +663,7 @@ for each file.
 
 [Stan](https://hackage.haskell.org/package/stan) is a Haskell static analysis
 tool. As of `stan-0.1.0.1`, it supports GHC >= 9.6.3 and Stack is built with
-GHC 9.6.5. The tool is configured by the contents of the `.stan.toml` file.
+GHC 9.6.6. The tool is configured by the contents of the `.stan.toml` file.
 
 This workflow will run if:
 

cabal.config

@@ -80,8 +80,8 @@ constraints:
   , generic-deriving ==1.14.5
   , generically ==0.1.1
   , ghc-bignum ==1.3
-  , ghc-boot ==9.6.5
-  , ghc-boot-th ==9.6.5
+  , ghc-boot ==9.6.6
+  , ghc-boot-th ==9.6.6
   , ghc-prim ==0.10.0
   , githash ==0.1.7.0
   , hackage-security ==0.6.2.4

cabal.project

@@ -33,8 +33,8 @@
 -- specified by the snapshot specifed in Stack's project-level YAML
 -- configuration file (`stack.yaml`). The relevant version of GHC can be
 -- confirmed by reviewing the snapshot on Stackage. For example, at:
--- https://www.stackage.org/lts-22.21/cabal.config.
+-- https://www.stackage.org/lts-22.28/cabal.config.
 --
-with-compiler: ghc-9.6.5
+with-compiler: ghc-9.6.6
 import: cabal.config
 packages: .

doc/GUIDE.md

@@ -258,7 +258,7 @@ packages:
 The value of the [`resolver`](yaml_configuration.md#resolver) key tells Stack
 *how* to build your package: which GHC version to use, versions of package
 dependencies, and so on. Our value here says to use
-[LTS Haskell 22.21](https://www.stackage.org/lts-22.21), which implies GHC 9.6.5
+[LTS Haskell 22.28](https://www.stackage.org/lts-22.28), which implies GHC 9.6.6
 (which is why `stack build` installs that version of GHC if it is not already
 available to Stack). There are a number of values you can use for `resolver`,
 which we'll cover later.
@@ -528,22 +528,22 @@ towards by default as well).
 Let's explore package sets a bit further. Instead of `lts-22.13`, let's change
 our `stack.yaml` file to use the
 [latest nightly](https://www.stackage.org/nightly). Right now, this is currently
-2024-03-20 - please see the snapshot from the link above to get the latest.
+2024-07-05 - please see the snapshot from the link above to get the latest.
 
 Then, commanding `stack build` again will produce:
 
 ~~~text
 stack build
-# Downloaded nightly-2024-03-20 build plan.
+# Downloaded nightly-2024-07-05 build plan.
 # build output ...
 ~~~
 
 We can also change snapshots on the command line, which can be useful in a
 Continuous Integration (CI) setting, like on Travis. For example, command:
 
 ~~~text
-stack --snapshot lts-21.25 build
-# Downloaded lts-21.25 build plan.
+stack --snapshot lts-22.27 build
+# Downloaded lts-22.27 build plan.
 # build output ...
 ~~~
 
@@ -982,7 +982,7 @@ stack purge
 stack build :helloworld-test
 helloworld> configure (lib + test)
 Configuring helloworld-0.1.0.0...
-helloworld> build (lib + test) with ghc-9.6.5
+helloworld> build (lib + test) with ghc-9.6.6
 Preprocessing library for helloworld-0.1.0.0..
 Building library for helloworld-0.1.0.0..
 [1 of 2] Compiling Lib
@@ -1300,7 +1300,7 @@ yields output like:
 
 ~~~text
 Run from outside a project, using implicit global project config
-Using latest snapshot resolver: lts-22.21
+Using latest snapshot resolver: lts-22.28
 Writing global (non-project-specific) config file to: /home/michael/.stack/global/stack.yaml
 Note: You can change the snapshot via the resolver field there.
 I installed the stm package via --package stm

doc/Stack_and_VS_Code.md

@@ -75,9 +75,9 @@ enabled). For further information about these options, see the `install-ghc`
 
 For this workaround to work, each time that a snapshot is used that references a
 different version of GHC, then GHCup must be used to install it (if GHCup has
-not already installed that version). For example, to use `snapshot: lts-22.21`
-(GHC 9.6.5), the command `ghcup install ghc 9.6.5` must have been used to
-install GHC 9.6.5. That may be a minor inconvenience for some people, as one the
+not already installed that version). For example, to use `snapshot: lts-22.28`
+(GHC 9.6.6), the command `ghcup install ghc 9.6.6` must have been used to
+install GHC 9.6.6. That may be a minor inconvenience for some people, as one the
 primary benefits of Stack over other tools for building Haskell code has been
 that Stack automatically ensures that the necessary version of GHC is available.
 

doc/custom_snapshot.md

@@ -18,8 +18,8 @@ available in snapshots to ensure reproducibility.
     for snapshot specification.
 
 ~~~yaml
-snapshot: lts-22.21 # Inherits GHC version and package set
-compiler: ghc-9.6.4 # Overwrites GHC version in the snapshot, optional
+snapshot: lts-22.28 # Inherits GHC version and package set
+compiler: ghc-9.6.5 # Overwrites GHC version in the snapshot, optional
 
 # Additional packages, follows extra-deps syntax
 packages:
@@ -62,35 +62,35 @@ custom snapshot, due to Stack sharing snapshot packages whenever possible.
 
 ### Overriding the compiler
 
-The following snapshot specification will be identical to `lts-22.21`, but
-instead use `ghc-9.6.4` instead of `ghc-9.6.5`:
+The following snapshot specification will be identical to `lts-22.28`, but
+instead use `ghc-9.6.5` instead of `ghc-9.6.6`:
 
 ~~~yaml
-snapshot: lts-22.21
-compiler: ghc-9.6.4
+snapshot: lts-22.28
+compiler: ghc-9.6.5
 ~~~
 
 ### Dropping packages
 
-The following snapshot specification will be identical to `lts-22.21`, but
+The following snapshot specification will be identical to `lts-22.28`, but
 without the `text` package in our snapshot. Removing this package will cause all
 the packages that depend on `text` to be unbuildable, but they will still be
 present in the snapshot.
 
 ~~~yaml
-snapshot: lts-22.21
+snapshot: lts-22.28
 drop-packages:
 - text
 ~~~
 
 ### Hiding packages
 
-The following snapshot specification will be identical to `lts-22.21`, but the
+The following snapshot specification will be identical to `lts-22.28`, but the
 `text` package will be hidden when registering. This will affect, for example,
 the import parser in the script command.
 
 ~~~yaml
-snapshot: lts-22.21
+snapshot: lts-22.28
 hidden:
 - text
 ~~~
@@ -100,11 +100,11 @@ hidden:
 In order to specify GHC options for a package, you use the same syntax as the
 [ghc-options](yaml_configuration.md#ghc-options) key for build configuration.
 
-The following snapshot specification will be identical to `lts-22.21`, but
+The following snapshot specification will be identical to `lts-22.28`, but
 provides `-O1` as a ghc-option for `text`:
 
 ~~~yaml
-snapshot: lts-22.21
+snapshot: lts-22.28
 packages:
 - text-2.0.2
 ghc-options:
@@ -123,11 +123,11 @@ packages in the `packages` list, rather than all packages in the snapshot.
 
 In order to specify Cabal flags for a package, you use the same syntax as the
 [flags](yaml_configuration.md#flags) key for build configuration. The
-following snapshot specification will be identical to `lts-22.21`, but
+following snapshot specification will be identical to `lts-22.28`, but
 it enables the `developer` Cabal flag:
 
 ~~~yaml
-snapshot: lts-22.21
+snapshot: lts-22.28
 packages:
 - text-2.0.2
 flags:

doc/faq.md

@@ -9,7 +9,7 @@ here is to be as helpful and concise as possible.
 ## What version of GHC is used when I run something like `stack ghci`?
 
 The version of GHC, as well as which packages can be installed, are specified by
-the _snapshot_. This may be something like `lts-22.21`, which is from
+the _snapshot_. This may be something like `lts-22.28`, which is from
 [Stackage](https://www.stackage.org/). The [user's guide](GUIDE.md) discusses
 the snapshot in more detail.
 
@@ -76,7 +76,7 @@ You can make tweaks to a snapshot by modifying the `extra-deps` configuration
 value in your `stack.yaml` file, e.g.:
 
 ~~~yaml
-snapshot: lts-22.21
+snapshot: lts-22.28
 packages:
 - .
 extra-deps:
@@ -91,7 +91,7 @@ Add it to the
 directory where your `stack.yaml` file lives, e.g.
 
 ~~~yaml
-snapshot: lts-22.21
+snapshot: lts-22.28
 packages:
 - .
 extra-deps:

doc/haskell_and_c_code.md

@@ -83,7 +83,7 @@ executables:
 
 The project's `stack.yaml` file only needs to identify a snapshot:
 ~~~yaml
-snapshot: lts-22.26 # GHC 9.6.5
+snapshot: lts-22.28 # GHC 9.6.6
 ~~~
 
 This example project can be built with Stack in the normal way (`stack build`),
@@ -220,7 +220,7 @@ The `include-dirs` key will cause the specified directory (again,
 
 The project's `stack.yaml` file only needs to identify a snapshot:
 ~~~yaml
-snapshot: lts-22.26 # GHC 9.6.5
+snapshot: lts-22.28 # GHC 9.6.6
 ~~~
 
 This example project can be built with Stack in the normal way (`stack build`),

doc/install_and_upgrade.md

@@ -417,7 +417,7 @@ GitHub repository.
         |GHC version|LLVM versions|
         |-----------|-------------|
         |9.8.2      |11 to 15     |
-        |9.6.5      |11 to 15     |
+        |9.6.6      |11 to 15     |
         |9.4.8      |10 to 14     |
         |9.2.8      |9 to 12      |
         |9.0.2      |9, 10 or 12  |

doc/list_command.md

@@ -30,11 +30,11 @@ For example:
 
 ~~~text
 stack list base unix Win32 acme-missiles pantry
-base-4.19.0.0
-unix-2.8.5.0
-Win32-2.13.4.0
+base-4.20.0.1
+unix-2.8.5.1
+Win32-2.14.0.0
 acme-missiles-0.3
-pantry-0.9.3.1
+pantry-0.10.0
 
 stack list paltry
 Could not find package paltry, updating
@@ -45,17 +45,17 @@ Error: [S-4926]
          pantry, pretty, pasty, xattr, alloy, para, pappy, alure, polar and
          factory.
 
-stack --snapshot lts-22.21 list base unix Win32 acme-missiles pantry
+stack --snapshot lts-22.28 list base unix Win32 acme-missiles pantry
 Error: [S-4926]
        * Package does not appear in snapshot (directly or indirectly): acme-missiles.
 
-stack --snapshot lts-22.21 list base unix Win32 pantry
+stack --snapshot lts-22.28 list base unix Win32 pantry
 base-4.18.2.1
 unix-2.8.4.0
 Win32-2.13.3.0
 pantry-0.9.3.2
 
-stack --snapshot lts-22.21 list
+stack --snapshot lts-22.28 list
 AC-Angle-1.0
 ALUT-2.4.0.3
 ...

doc/script_command.md

@@ -20,7 +20,7 @@ Stack root). Consequently, a snapshot must be specified on the command line
 (with the `--snapshot` option). For example:
 
 ~~~text
-stack script --snapshot lts-22.21 MyScript.hs
+stack script --snapshot lts-22.28 MyScript.hs
 ~~~
 
 !!! info
@@ -109,7 +109,7 @@ main = do
 can be compiled and run, with arguments, with:
 
 ~~~text
-stack --snapshot lts-22.21 script --package acme-missiles --compile MyScript.hs -- "Don't panic!" "Duck and cover!"
+stack --snapshot lts-22.28 script --package acme-missiles --compile MyScript.hs -- "Don't panic!" "Duck and cover!"
 ~~~
 
 All the compilation outputs (like `Main.hi`, `Main.o`, and the executable

doc/scripts.md

@@ -19,7 +19,7 @@ An example will be easiest to understand. Consider the Haskell source file
 
 ~~~haskell
 #!/usr/bin/env stack
--- stack script --snapshot lts-22.21 --package turtle
+-- stack script --snapshot lts-22.28 --package turtle
 {-# LANGUAGE OverloadedStrings #-}
 import Turtle (echo)
 main = echo "Hello World!"
@@ -78,10 +78,10 @@ able to reuse everything already built).
 
 The second line of the source code is the Stack interpreter options comment. In
 this example, it specifies the [`stack script`](script_command.md) command with
-the options of a LTS Haskell 22.21 snapshot (`--snapshot lts-22.21`) and
+the options of a LTS Haskell 22.28 snapshot (`--snapshot lts-22.28`) and
 ensuring the [`turtle` package](https://hackage.haskell.org/package/turtle) is
 available (`--package turtle`). The version of the package will be that in the
-specified snapshot (`lts-22.21` provides `turtle-1.6.2`).
+specified snapshot (`lts-22.28` provides `turtle-1.6.2`).
 
 ## Arguments and interpreter options and arguments
 
@@ -116,7 +116,7 @@ For example, the command `stack MyScript.hs arg1 arg2` with `MyScript.hs`:
 ~~~haskell
 #!/usr/bin/env stack
 {- stack script
-   --snapshot lts-22.21
+   --snapshot lts-22.28
    --
    +RTS -s -RTS
 -}
@@ -132,7 +132,7 @@ main = do
 is equivalent to the following command at the command line:
 
 ~~~text
-stack script --snapshot lts-22.21 -- MyScript.hs arg1 arg2 +RTS -s -RTS
+stack script --snapshot lts-22.28 -- MyScript.hs arg1 arg2 +RTS -s -RTS
 ~~~
 
 where `+RTS -s -RTS` are some of GHC's
@@ -161,7 +161,7 @@ providing a comma or space separated list. For example:
 ~~~haskell
 #!/usr/bin/env stack
 {- stack script
-   --snapshot lts-22.21
+   --snapshot lts-22.28
    --package turtle
    --package "stm async"
    --package http-client,http-conduit
@@ -202,7 +202,7 @@ which makes use of the joke package
 
 ~~~haskell
 {- stack script
-   --snapshot lts-22.21
+   --snapshot lts-22.28
    --package acme-missiles
 -}
 import Acme.Missiles (launchMissiles)
@@ -213,7 +213,7 @@ main = launchMissiles
 
 The command `stack --script-no-run-compile Script.hs` then behaves as if the
 command
-`stack script --snapshot lts-22.21 --package acme-missiles --no-run --compile -- Script.hs`
+`stack script --snapshot lts-22.28 --package acme-missiles --no-run --compile -- Script.hs`
 had been given. `Script.hs` is compiled (without optimisation) and the resulting
 executable is not run: no missiles are launched in the process!
 
@@ -252,7 +252,7 @@ here is an example with [`stack runghc`](runghc_command.md):
 {- stack
   runghc
   --install-ghc
-  --snapshot lts-22.21
+  --snapshot lts-22.28
   --package base
   --package turtle
   --
@@ -276,7 +276,7 @@ it. Here is an example:
 {- stack
    exec ghci
    --install-ghc
-   --snapshot lts-22.21
+   --snapshot lts-22.28
    --package turtle
 -}
 ~~~