Bump to Stackage LTS Haskell 23.24

Author: mpilgrem

CONTRIBUTING.md

@@ -348,9 +348,9 @@ compatibility with a range of versions of GHC that a library package (such as
 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 2025) the package versions are
-primarily ones in Stackage snapshot LTS Haskell 23.17 (for GHC 9.8.4) and
-`hpack-0.38.1`, `pantry-0.10.1` and `tls-2.1.8`.
+any time. At the time of writing (June 2025) the package versions are
+primarily ones in Stackage snapshot LTS Haskell 23.24 (for GHC 9.8.4) and
+`hpack-0.38.1` and `tls-2.1.8`.
 
 A Stack executable makes use of Cabal (the library) through a small 'Setup'
 executable that it compiles from Haskell source code. The executable compiles

cabal.config

@@ -29,7 +29,7 @@ constraints:
   , bifunctors ==5.6.2
   , binary ==0.8.9.1
   , bitvec ==1.1.5.0
-  , blaze-builder ==0.4.2.3
+  , blaze-builder ==0.4.3
   , blaze-html ==0.9.2.0
   , blaze-markup ==0.8.3.0
   , byteorder ==1.0.4
@@ -50,11 +50,11 @@ constraints:
   , conduit-extra ==1.3.7
   , containers ==0.6.8
   , contravariant ==1.5.5
-  , cookie ==0.5.0
+  , cookie ==0.5.1
   , cryptohash-sha256 ==0.11.102.1
-  , crypton ==1.0.3
+  , crypton ==1.0.4
   , crypton-conduit ==0.2.3
-  , crypton-connection ==0.4.3
+  , crypton-connection ==0.4.4
   , crypton-x509 ==1.7.7
   , crypton-x509-store ==1.6.10
   , crypton-x509-system ==1.6.7
@@ -79,15 +79,15 @@ constraints:
   , file-embed ==0.0.16.0
   , filelock ==0.1.1.7
   , filepath ==1.4.301.0
-  , fsnotify ==0.4.2.0
+  , fsnotify ==0.4.3.0
   , generic-deriving ==1.14.6
   , generically ==0.1.1
   , ghc-bignum ==1.3
   , ghc-boot ==9.8.4
   , ghc-boot-th ==9.8.4
   , ghc-prim ==0.11.0
   , githash ==0.1.7.0
-  , hackage-security ==0.6.2.6
+  , hackage-security ==0.6.3.0
   , half ==0.3.2
   , happy ==2.0.2
   , happy-lib ==2.0.2
@@ -98,7 +98,7 @@ constraints:
   , hourglass ==0.2.12
   , hpack ==0.38.1
   , hpc ==0.7.0.0
-  , http-api-data ==0.6.1
+  , http-api-data ==0.6.2
   , http-client ==0.7.19
   , http-client-tls ==0.3.6.4
   , http-conduit ==2.3.9.1
@@ -115,7 +115,6 @@ constraints:
   , libyaml-clib ==0.2.5
   , lift-type ==0.1.2.0
   , lifted-base ==0.2.3.12
-  , lukko ==0.1.2
   , megaparsec ==9.6.1
   , memory ==0.18.0
   , microlens ==0.4.13.1
@@ -129,7 +128,7 @@ constraints:
   , mono-traversable ==1.0.21.0
   , mtl ==2.3.1
   , mtl-compat ==0.2.2
-  , mustache ==2.4.2
+  , mustache ==2.4.3.1
   , neat-interpolation ==0.5.1.4
   , network ==3.2.7.0
   , network-uri ==2.6.4.2
@@ -152,7 +151,7 @@ constraints:
   , pretty ==1.1.3.6
   , prettyprinter ==1.7.1
   , prettyprinter-ansi-terminal ==1.1.3
-  , primitive ==0.9.0.0
+  , primitive ==0.9.1.0
   , process ==1.6.25.0
   , project-template ==0.2.1.0
   , random ==1.2.1.3
@@ -206,7 +205,7 @@ constraints:
   , transformers ==0.6.1.0
   , transformers-base ==0.4.6
   , transformers-compat ==0.7.2
-  , typed-process ==0.2.12.0
+  , typed-process ==0.2.13.0
   , unix ==2.8.6.0
   , unix-compat ==0.7.4
   , unix-time ==0.4.16

cabal.project

@@ -33,7 +33,7 @@
 -- 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-23.17/cabal.config.
+-- https://www.stackage.org/lts-23.24/cabal.config.
 --
 with-compiler: ghc-9.8.4
 import: cabal.config

doc/commands/list_command.md

@@ -34,7 +34,7 @@ base-4.21.0.0
 unix-2.8.6.0
 Win32-2.14.1.0
 acme-missiles-0.3
-pantry-0.10.0
+pantry-0.10.1
 
 stack list paltry
 Could not find package paltry, updating
@@ -45,17 +45,17 @@ Error: [S-4926]
          tasty, retry, path, pretty, pasty, xattr, alloy, para, pappy and
          alure.
 
-stack --snapshot lts-23.17 list base unix Win32 acme-missiles pantry
+stack --snapshot lts-23.24 list base unix Win32 acme-missiles pantry
 Error: [S-4926]
        * Package does not appear in snapshot (directly or indirectly): acme-missiles.
 
-stack --snapshot lts-23.17 list base unix Win32 pantry
+stack --snapshot lts-23.24 list base unix Win32 pantry
 base-4.19.2.0
 unix-2.8.6.0
 Win32-2.13.4.0
-pantry-0.10.0
+pantry-0.10.1
 
-stack --snapshot lts-23.17 list
+stack --snapshot lts-23.24 list
 AC-Angle-1.0
 ALUT-2.4.0.3
 ...

doc/commands/script_command.md

@@ -49,7 +49,7 @@ A snapshot must be specified on the command line, using the `--snapshot` option.
 For example:
 
 ~~~text
-stack script --snapshot lts-23.17 MyScript.hs
+stack script --snapshot lts-23.24 MyScript.hs
 ~~~
 
 An immutable extra-dep can be added to the snapshot on the command line with the
@@ -211,7 +211,7 @@ main = do
 can be compiled and run, with arguments, with:
 
 ~~~text
-stack --snapshot lts-23.17 script --package acme-missiles --compile MyScript.hs -- "Don't panic!" "Duck and cover!"
+stack --snapshot lts-23.24 script --package acme-missiles --compile MyScript.hs -- "Don't panic!" "Duck and cover!"
 ~~~
 
 `acme-missiles-0.3` (the most recent version in the package index) will be used.
@@ -231,7 +231,7 @@ snapshot as an extra-dep. The `stack script` command is specified using Stack's
 
 ~~~haskell
 {- stack script
-   -- snapshot lts-23.17
+   -- snapshot lts-23.24
    -- extra-dep acme-missiles-0.2
    -- package acme-missiles
 -}
@@ -333,7 +333,7 @@ A Haskell source file `MyScript.hs`, as follows:
 
 ~~~haskell
 {- stack script
-   --snapshot lts-23.17
+   --snapshot lts-23.24
 -}
 
 {-# LANGUAGE OverloadedStrings #-}

doc/configure/yaml/non-project.md

@@ -299,7 +299,7 @@ snapshots like `ghc-9.8.4`. This can be used to override the compiler for a
 Stackage snapshot, like this:
 
 ~~~yaml
-snapshot: lts-23.17
+snapshot: lts-23.24
 compiler: ghc-9.8.3
 compiler-check: match-exact
 ~~~

doc/configure/yaml/project.md

@@ -40,8 +40,8 @@ installation, and various settings like build flags. It is also called a
 resolver since a snapshot states how dependencies are resolved. There are
 currently four snapshot types:
 
-* LTS Haskell snapshots, e.g. `snapshot: lts-23.17`
-* Stackage Nightly snapshots, e.g. `snapshot: nightly-2025-04-05`
+* LTS Haskell snapshots, e.g. `snapshot: lts-23.24`
+* Stackage Nightly snapshots, e.g. `snapshot: nightly-2025-06-15`
 * No snapshot, just use packages shipped with the compiler. For GHC this looks
   like `snapshot: ghc-9.8.4`
 * Custom snapshot, via a URL or relative file path. For further information, see

doc/topics/Stack_and_VS_Code.md

@@ -150,7 +150,7 @@ VS Code with the 'Haskell' extension can be configured in a number of ways:
 
         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-23.17`
+        installed that version). For example, to use `snapshot: lts-23.24`
         (GHC 9.8.4), the command `ghcup install ghc 9.8.4` must have been used
         to install GHC 9.8.4. That may be a minor inconvenience for some people,
         as one the primary benefits of Stack over other tools for building

doc/topics/custom_snapshot.md

@@ -18,7 +18,7 @@ available in snapshots to ensure reproducibility.
     for snapshot specification.
 
 ~~~yaml
-snapshot: lts-23.17 # Inherits GHC version and package set
+snapshot: lts-23.24 # Inherits GHC version and package set
 compiler: ghc-9.8.3 # Overwrites GHC version in the snapshot, optional
 
 # Additional packages, follows extra-deps syntax
@@ -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-23.17`, but
+The following snapshot specification will be identical to `lts-23.24`, but
 instead use `ghc-9.8.3` instead of `ghc-9.8.4`:
 
 ~~~yaml
-snapshot: lts-23.17
+snapshot: lts-23.24
 compiler: ghc-9.8.3
 ~~~
 
 ### Dropping packages
 
-The following snapshot specification will be identical to `lts-23.17`, but
+The following snapshot specification will be identical to `lts-23.24`, 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-23.17
+snapshot: lts-23.24
 drop-packages:
 - text
 ~~~
 
 ### Hiding packages
 
-The following snapshot specification will be identical to `lts-23.17`, but the
+The following snapshot specification will be identical to `lts-23.24`, but the
 `text` package will be hidden when registering. This will affect, for example,
 the import parser in the script command.
 
 ~~~yaml
-snapshot: lts-23.17
+snapshot: lts-23.24
 hidden:
 - text
 ~~~
@@ -101,11 +101,11 @@ In order to specify GHC options for a package, you use the same syntax as the
 [ghc-options](../configure/yaml/non-project.md#ghc-options) key for build
 configuration.
 
-The following snapshot specification will be identical to `lts-23.17`, but
+The following snapshot specification will be identical to `lts-23.24`, but
 provides `-O1` as a ghc-option for `text`:
 
 ~~~yaml
-snapshot: lts-23.17
+snapshot: lts-23.24
 packages:
 - text-2.0.2
 ghc-options:
@@ -124,11 +124,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](../configure/yaml/project.md#flags) key for build configuration. The
-following snapshot specification will be identical to `lts-23.17`, but
+following snapshot specification will be identical to `lts-23.24`, but
 it enables the `developer` Cabal flag:
 
 ~~~yaml
-snapshot: lts-23.17
+snapshot: lts-23.24
 packages:
 - text-2.0.2
 flags:

doc/topics/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-23.17 # GHC 9.8.4
+snapshot: lts-23.24 # GHC 9.8.4
 ~~~
 
 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-23.17 # GHC 9.8.4
+snapshot: lts-23.24 # GHC 9.8.4
 ~~~
 
 This example project can be built with Stack in the normal way (`stack build`),