Merge pull request #6793 from commercialhaskell/lts-24.3

Bump to Stackage LTS Haskell 24.4

Author: mpilgrem

CONTRIBUTING.md

@@ -348,8 +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 (June 2025) the package versions are
-primarily ones in Stackage snapshot LTS Haskell 24.0 (for GHC 9.10.2).
+any time. At the time of writing (August 2025) the package versions are
+primarily ones in Stackage snapshot LTS Haskell 24.4 (for GHC 9.10.2) and
+`pantry-0.11.0`.
 
 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

@@ -9,8 +9,8 @@ constraints:
   , aeson ==2.2.3.0
   , aeson-warning-parser ==0.1.1
   , annotated-wl-pprint ==0.7.0
-  , ansi-terminal ==1.1.2
-  , ansi-terminal-types ==1.1
+  , ansi-terminal ==1.1.3
+  , ansi-terminal-types ==1.1.3
   , appar ==0.1.8
   , array ==0.5.8.0
   , asn1-encoding ==0.9.6
@@ -30,7 +30,7 @@ constraints:
   , bifunctors ==5.6.2
   , binary ==0.8.9.3
   , bitvec ==1.1.5.0
-  , blaze-builder ==0.4.3
+  , blaze-builder ==0.4.4
   , blaze-html ==0.9.2.0
   , blaze-markup ==0.8.3.0
   , byteorder ==1.0.4
@@ -55,9 +55,10 @@ constraints:
   , cryptohash-sha256 ==0.11.102.1
   , crypton ==1.0.4
   , crypton-conduit ==0.2.3
-  , crypton-connection ==0.4.4
+  , crypton-connection ==0.4.5
+  , crypton-socks ==0.6.2
   , crypton-x509 ==1.7.7
-  , crypton-x509-store ==1.6.10
+  , crypton-x509-store ==1.6.11
   , crypton-x509-system ==1.6.7
   , crypton-x509-validation ==1.6.14
   , data-default ==0.8.0.1
@@ -91,8 +92,8 @@ constraints:
   , githash ==0.1.7.0
   , hackage-security ==0.6.3.1
   , half ==0.3.3
-  , happy ==2.1.5
-  , happy-lib ==2.1.5
+  , happy ==2.1.6
+  , happy-lib ==2.1.6
   , hashable ==1.5.0.0
   , haskell-src-exts ==1.23.1
   , haskell-src-meta ==0.8.15
@@ -140,7 +141,7 @@ constraints:
   , optparse-applicative ==0.18.1.0
   , optparse-simple ==0.1.1.4
   , os-string ==2.0.4
-  , pantry ==0.10.1
+  , pantry ==0.11.0
   , parsec ==3.1.18.0
   , parser-combinators ==1.3.0
   , path ==0.9.6
@@ -172,7 +173,6 @@ constraints:
   , semigroupoids ==6.0.1
   , serialise ==0.2.6.1
   , silently ==1.2.5.4
-  , socks ==0.6.1
   , split ==0.2.5
   , splitmix ==0.1.3.1
   , stack ==3.8.0

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-24.0/cabal.config.
+-- https://www.stackage.org/lts-24.4/cabal.config.
 --
 with-compiler: ghc-9.10.2
 import: cabal.config

doc/commands/list_command.md

@@ -45,17 +45,17 @@ Error: [S-4926]
          tasty, retry, path, pretty, pasty, xattr, alloy, para, pappy and
          alure.
 
-stack --snapshot lts-24.0 list base unix Win32 acme-missiles pantry
+stack --snapshot lts-24.4 list base unix Win32 acme-missiles pantry
 Error: [S-4926]
        * Package does not appear in snapshot (directly or indirectly): acme-missiles.
 
-stack --snapshot lts-24.0 list base unix Win32 pantry
+stack --snapshot lts-24.4 list base unix Win32 pantry
 base-4.20.1.0
 unix-2.8.6.0
 Win32-2.14.1.0
 pantry-0.10.1
 
-stack --snapshot lts-24.0 list
+stack --snapshot lts-24.4 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-24.0 MyScript.hs
+stack script --snapshot lts-24.4 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-24.0 script --package acme-missiles --compile MyScript.hs -- "Don't panic!" "Duck and cover!"
+stack --snapshot lts-24.4 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-24.0
+   -- snapshot lts-24.4
    -- 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-24.0
+   --snapshot lts-24.4
 -}
 
 {-# LANGUAGE OverloadedStrings #-}

doc/configure/yaml/non-project.md

@@ -300,7 +300,7 @@ can be used to override the compiler (and, implicitly, its boot packages) for a
 Stackage snapshot, like this:
 
 ~~~yaml
-snapshot: lts-24.0
+snapshot: lts-24.4
 compiler: ghc-9.10.1
 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-24.0`
-* Stackage Nightly snapshots, e.g. `snapshot: nightly-2025-07-14`
+* LTS Haskell snapshots, e.g. `snapshot: lts-24.4`
+* Stackage Nightly snapshots, e.g. `snapshot: nightly-2025-08-17`
 * No snapshot, just use packages shipped with the compiler. For GHC this looks
   like `snapshot: ghc-9.10.2`
 * 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-24.0`
+        installed that version). For example, to use `snapshot: lts-24.4`
         (GHC 9.10.2), the command `ghcup install ghc 9.10.2` must have been used
         to install GHC 9.10.2. 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

@@ -30,7 +30,7 @@ available in snapshots to ensure reproducibility.
 ~~~yaml
 # Inherits a specific GHC version and, implicitly, its boot packages and
 # specific versions of a set of other packages:
-snapshot: lts-24.0
+snapshot: lts-24.4
 # Overwrites the version of GHC (and, implicitly, its boot packages) specified
 # in the snapshot (optional):
 compiler: ghc-9.10.1
@@ -76,36 +76,36 @@ custom snapshot, due to Stack sharing snapshot packages whenever possible.
 
 ### Overriding the compiler
 
-The following snapshot specification will be identical to `lts-24.0`, but
+The following snapshot specification will be identical to `lts-24.4`, but
 instead use `ghc-9.10.1` and its boot packages instead of `ghc-9.10.2` and its
 boot packages:
 
 ~~~yaml
-snapshot: lts-24.0 # GHC 9.10.2
+snapshot: lts-24.4 # GHC 9.10.2
 compiler: ghc-9.10.1
 ~~~
 
 ### Dropping packages
 
-The following snapshot specification will be identical to `lts-24.0`, but
+The following snapshot specification will be identical to `lts-24.4`, 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-24.0
+snapshot: lts-24.4
 drop-packages:
 - text
 ~~~
 
 ### Hiding packages
 
-The following snapshot specification will be identical to `lts-24.0`, but the
+The following snapshot specification will be identical to `lts-24.4`, but the
 `text` package will be hidden when registering. This will affect, for example,
 the import parser in the script command.
 
 ~~~yaml
-snapshot: lts-24.0
+snapshot: lts-24.4
 hidden:
 - text
 ~~~
@@ -116,11 +116,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-24.0`, but
+The following snapshot specification will be identical to `lts-24.4`, but
 provides `-O1` as a ghc-option for `text`:
 
 ~~~yaml
-snapshot: lts-24.0
+snapshot: lts-24.4
 packages:
 - text-2.1.2
 ghc-options:
@@ -139,11 +139,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-24.0`, but
+following snapshot specification will be identical to `lts-24.4`, but
 it enables the `developer` Cabal flag:
 
 ~~~yaml
-snapshot: lts-24.0
+snapshot: lts-24.4
 packages:
 - text-2.1.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-24.0 # GHC 9.10.2
+snapshot: lts-24.4 # GHC 9.10.2
 ~~~
 
 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-24.0 # GHC 9.10.2
+snapshot: lts-24.4 # GHC 9.10.2
 ~~~
 
 This example project can be built with Stack in the normal way (`stack build`),