Bump to Stackage LTS Haskell 24.55

CONTRIBUTING.md

@@ -352,10 +352,10 @@ 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 2026) the package versions are
-primarily ones in Stackage snapshot LTS Haskell 24.43 (for GHC 9.10.3), the
-latest version of `Cabal` released on Hackage (`Cabal-3.16.1.0`),
-`pantry-0.11.2`, `persistent-2.18.1.0` and the latest version of packages in
-the `tls` family (which reduce dependencies on unmaintained packages).
+primarily ones in Stackage snapshot LTS Haskell 24.55 (for GHC 9.10.3),
+`Cabal-3.16.1.0`, `pantry-0.11.2`, `persistent-2.18.1.0` and the latest version
+of packages in the `tls` family (which reduce dependencies on unmaintained
+packages).
 
 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.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.43/cabal.config.
+-- https://www.stackage.org/lts-24.55/cabal.config.
 --
 with-compiler: ghc-9.10.3
 import: cabal.config

doc/commands/build_command.md

@@ -1282,7 +1282,7 @@ Examples:
     the most recent Stackage Nightly snapshot:
 
     ~~~text
-    stack --snapshot nightly install Agda-2.6.3
+    stack --snapshot nightly install Agda-2.8.0
     ~~~
 
     Alternatively, Stack can be used to unpack the package from the package

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.43 list base unix Win32 acme-missiles pantry
+stack --snapshot lts-24.55 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.43 list base unix Win32 pantry
+stack --snapshot lts-24.55 list base unix Win32 pantry
 base-4.20.2.0
 unix-2.8.7.0
 Win32-2.14.1.0
 pantry-0.10.1
 
-stack --snapshot lts-24.43 list
+stack --snapshot lts-24.55 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.43 MyScript.hs
+stack script --snapshot lts-24.55 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.43 script --package acme-missiles --compile MyScript.hs -- "Don't panic!" "Duck and cover!"
+stack --snapshot lts-24.55 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.43
+   -- snapshot lts-24.55
    -- 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.43
+   --snapshot lts-24.55
 -}
 
 {-# LANGUAGE OverloadedStrings #-}

doc/configure/yaml/include.md

@@ -28,10 +28,10 @@ A value for a key can be provided by an included file. For example, given a file
 `snapshot.yaml` in the project directory with the content:
 
 ~~~yaml
-lts-24.43
+lts-24.55
 ~~~
 
-the following project-level configuration file would use `lts-24.43` as the
+the following project-level configuration file would use `lts-24.55` as the
 snapshot:
 
 ~~~yaml
@@ -42,7 +42,7 @@ The included file replaces the `!include` directive with its content, so this is
 equivalent to:
 
 ~~~yaml
-snapshot: lts-24.43
+snapshot: lts-24.55
 ~~~
 
 ## Including a sequence
@@ -59,7 +59,7 @@ directory with the content:
 the following project-level configuration file would use those as extra-deps:
 
 ~~~yaml
-snapshot: lts-24.43
+snapshot: lts-24.55
 extra-deps: !include extra-deps.yaml
 ~~~
 
@@ -83,14 +83,14 @@ flags:
 the following project-level configuration file would merge those options:
 
 ~~~yaml
-snapshot: lts-24.43
+snapshot: lts-24.55
 <<: !include shared-config.yaml
 ~~~
 
 This is equivalent to:
 
 ~~~yaml
-snapshot: lts-24.43
+snapshot: lts-24.55
 ghc-options:
   "$everything": -Wall
 flags:
@@ -101,7 +101,7 @@ flags:
 The `!include` directive can also be placed on the line after the merge key:
 
 ~~~yaml
-snapshot: lts-24.43
+snapshot: lts-24.55
 <<:
   !include shared-config.yaml
 ~~~

doc/configure/yaml/non-project.md

@@ -317,7 +317,7 @@ can be used to override the compiler (and, implicitly, its boot packages) for a
 Stackage snapshot, like this:
 
 ~~~yaml
-snapshot: lts-24.43
+snapshot: lts-24.55
 compiler: ghc-9.10.2
 compiler-check: match-exact
 ~~~

doc/configure/yaml/project.md

@@ -39,13 +39,13 @@ snapshot defines a GHC version, the package version of packages available for
 installation, and various settings like build flags. For example:
 
 ~~~yaml
-snapshot: lts-24.43 # A Stackage LTS Haskell snapshot
+snapshot: lts-24.55 # A Stackage LTS Haskell snapshot
 ~~~
 
 or
 
 ~~~yaml
-snapshot: nightly-2026-05-29 # A Stackage Nightly snapshot
+snapshot: nightly-2026-08-20 # A Stackage Nightly snapshot
 ~~~
 
 For further information about how to specify the location of a snapshot, see the

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.43`
+        installed that version). For example, to use `snapshot: lts-24.55`
         (GHC 9.10.3), the command `ghcup install ghc 9.10.3` must have been used
         to install GHC 9.10.3. 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

@@ -29,7 +29,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.43
+snapshot: lts-24.55
 # Overwrites the version of GHC (and, implicitly, its boot packages) specified
 # in the snapshot (optional):
 compiler: ghc-9.10.2
@@ -80,36 +80,36 @@ custom snapshot, due to Stack sharing snapshot packages whenever possible.
 
 ### Overriding the compiler
 
-The following snapshot specification will be identical to `lts-24.43`, but
+The following snapshot specification will be identical to `lts-24.55`, but
 instead use `ghc-9.10.2` and its boot packages instead of `ghc-9.10.3` and its
 boot packages:
 
 ~~~yaml
-snapshot: lts-24.43 # GHC 9.10.3
+snapshot: lts-24.55 # GHC 9.10.3
 compiler: ghc-9.10.2
 ~~~
 
 ### Dropping packages
 
-The following snapshot specification will be identical to `lts-24.43`, but
+The following snapshot specification will be identical to `lts-24.55`, 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.43
+snapshot: lts-24.55
 drop-packages:
 - text
 ~~~
 
 ### Hiding packages
 
-The following snapshot specification will be identical to `lts-24.43`, but the
+The following snapshot specification will be identical to `lts-24.55`, 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.43
+snapshot: lts-24.55
 hidden:
 - text
 ~~~
@@ -120,11 +120,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.43`, but
+The following snapshot specification will be identical to `lts-24.55`, but
 provides `-O1` as a ghc-option for `text`:
 
 ~~~yaml
-snapshot: lts-24.43
+snapshot: lts-24.55
 packages:
 - text-2.1.2
 ghc-options:
@@ -143,11 +143,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.43`, but
+following snapshot specification will be identical to `lts-24.55`, but
 it enables the `developer` Cabal flag:
 
 ~~~yaml
-snapshot: lts-24.43
+snapshot: lts-24.55
 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.43 # GHC 9.10.3
+snapshot: lts-24.55 # GHC 9.10.3
 ~~~
 
 This example project can be built with Stack in the normal way (`stack build`),
@@ -221,7 +221,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.43 # GHC 9.10.3
+snapshot: lts-24.55 # GHC 9.10.3
 ~~~
 
 This example project can be built with Stack in the normal way (`stack build`),

doc/topics/lock_files.md

@@ -49,7 +49,7 @@ Relevant to this discussion, Stack's project-level configuration file
 Some of this information can be incomplete. Consider this `stack.yaml` file:
 
 ~~~yaml
-snapshot: lts-24.43
+snapshot: lts-24.55
 extra-deps:
 - acme-missiles-0.3
 ~~~
@@ -66,7 +66,7 @@ extra-deps:
     sha256: 614bc0cca76937507ea0a5ccc17a504c997ce458d7f2f9e43b15a10c8eaeb033
 ~~~
 
-The `lts-24.43` information is also incomplete. While we assume in general that
+The `lts-24.55` information is also incomplete. While we assume in general that
 Haskell LTS snapshots never change, there is nothing that prohibits that from
 happening. Instead, the complete version of that key is:
 
@@ -134,7 +134,7 @@ snapshots:
     sha256: 3c412a7c13dba6d3d808455a458e0776c58b6cf99b8a7961a2f5e55589d6f1d6
     size: 729011
     url: https://raw.githubusercontent.com/commercialhaskell/stackage-snapshots/master/lts/24/43.yaml
-  original: lts-24.43
+  original: lts-24.55
 ~~~
 
 ## Creation procedure