Merge pull request #6662 from commercialhaskell/lts-22.43

Bump stack.yaml to lts-22.43

Author: mpilgrem

CONTRIBUTING.md

@@ -348,10 +348,10 @@ 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 (september 2024) the package versions are
-primarily 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`, `tar`,
-`tls` and `crypton-connection`.
+any time. At the time of writing (December 2024) the package versions are
+primarily ones in Stackage snapshot LTS Haskell 22.43 (for GHC 9.6.6), together
+with extra-deps to depend on the latest versions of `crypton-connection`,
+`hpack`, `pantry`, `tar` and `tls`.
 
 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-22.28/cabal.config.
+-- https://www.stackage.org/lts-22.43/cabal.config.
 --
 with-compiler: ghc-9.6.6
 import: cabal.config

doc/commands/list_command.md

@@ -45,17 +45,17 @@ Error: [S-4926]
          pantry, pretty, pasty, xattr, alloy, para, pappy, alure, polar and
          factory.
 
-stack --snapshot lts-22.28 list base unix Win32 acme-missiles pantry
+stack --snapshot lts-22.43 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.28 list base unix Win32 pantry
+stack --snapshot lts-22.43 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.28 list
+stack --snapshot lts-22.43 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-22.28 MyScript.hs
+stack script --snapshot lts-22.43 MyScript.hs
 ~~~
 
 A package version can be added to the snapshot on the command line with the
@@ -187,7 +187,7 @@ main = do
 can be compiled and run, with arguments, with:
 
 ~~~text
-stack --snapshot lts-22.28 script --package acme-missiles --compile MyScript.hs -- "Don't panic!" "Duck and cover!"
+stack --snapshot lts-22.43 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.
@@ -207,7 +207,7 @@ snapshot as an extra-dep. The `stack script` command is specified using Stack's
 
 ~~~haskell
 {- stack script
-   -- snapshot lts-22.28
+   -- snapshot lts-22.43
    -- extra-dep acme-missiles-0.2
    -- package acme-missiles
 -}
@@ -309,7 +309,7 @@ A Haskell source file `MyScript.hs`, as follows:
 
 ~~~haskell
 {- stack script
-   --snapshot lts-22.28
+   --snapshot lts-22.43
 -}
 
 {-# LANGUAGE OverloadedStrings #-}

doc/configure/yaml/non-project.md

@@ -294,7 +294,7 @@ snapshots like `ghc-9.6.6`. This can be used to override the compiler for a
 Stackage snapshot, like this:
 
 ~~~yaml
-snapshot: lts-22.28
+snapshot: lts-22.43
 compiler: ghc-9.6.5
 compiler-check: match-exact
 ~~~

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-22.28`
+        installed that version). For example, to use `snapshot: lts-22.43`
         (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

doc/topics/custom_snapshot.md

@@ -18,7 +18,7 @@ available in snapshots to ensure reproducibility.
     for snapshot specification.
 
 ~~~yaml
-snapshot: lts-22.28 # Inherits GHC version and package set
+snapshot: lts-22.43 # Inherits GHC version and package set
 compiler: ghc-9.6.5 # 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-22.28`, but
+The following snapshot specification will be identical to `lts-22.43`, but
 instead use `ghc-9.6.5` instead of `ghc-9.6.6`:
 
 ~~~yaml
-snapshot: lts-22.28
+snapshot: lts-22.43
 compiler: ghc-9.6.5
 ~~~
 
 ### Dropping packages
 
-The following snapshot specification will be identical to `lts-22.28`, but
+The following snapshot specification will be identical to `lts-22.43`, 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.28
+snapshot: lts-22.43
 drop-packages:
 - text
 ~~~
 
 ### Hiding packages
 
-The following snapshot specification will be identical to `lts-22.28`, but the
+The following snapshot specification will be identical to `lts-22.43`, 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.28
+snapshot: lts-22.43
 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-22.28`, but
+The following snapshot specification will be identical to `lts-22.43`, but
 provides `-O1` as a ghc-option for `text`:
 
 ~~~yaml
-snapshot: lts-22.28
+snapshot: lts-22.43
 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-22.28`, but
+following snapshot specification will be identical to `lts-22.43`, but
 it enables the `developer` Cabal flag:
 
 ~~~yaml
-snapshot: lts-22.28
+snapshot: lts-22.43
 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-22.28 # GHC 9.6.6
+snapshot: lts-22.43 # 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.28 # GHC 9.6.6
+snapshot: lts-22.43 # GHC 9.6.6
 ~~~
 
 This example project can be built with Stack in the normal way (`stack build`),

doc/topics/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.28 --package turtle
+-- stack script --snapshot lts-22.43 --package turtle
 {-# LANGUAGE OverloadedStrings #-}
 import Turtle (echo)
 main = echo "Hello World!"
@@ -78,11 +78,11 @@ 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`](../commands/script_command.md)
-command with the options of a LTS Haskell 22.28 snapshot
-(`--snapshot lts-22.28`) and ensuring the
+command with the options of a LTS Haskell 22.43 snapshot
+(`--snapshot lts-22.43`) and ensuring the
 [`turtle`](https://hackage.haskell.org/package/turtle) package is available
 (`--package turtle`). The version of the package will be that in the specified
-snapshot (`lts-22.28` provides `turtle-1.6.2`).
+snapshot (`lts-22.43` provides `turtle-1.6.2`).
 
 ## Arguments and interpreter options and arguments
 
@@ -117,7 +117,7 @@ For example, the command `stack MyScript.hs arg1 arg2` with `MyScript.hs`:
 ~~~haskell
 #!/usr/bin/env stack
 {- stack script
-   --snapshot lts-22.28
+   --snapshot lts-22.43
    --
    +RTS -s -RTS
 -}
@@ -133,7 +133,7 @@ main = do
 is equivalent to the following command at the command line:
 
 ~~~text
-stack script --snapshot lts-22.28 -- MyScript.hs arg1 arg2 +RTS -s -RTS
+stack script --snapshot lts-22.43 -- MyScript.hs arg1 arg2 +RTS -s -RTS
 ~~~
 
 where `+RTS -s -RTS` are some of GHC's
@@ -162,7 +162,7 @@ options, or by providing a comma or space separated list. For example:
 ~~~haskell
 #!/usr/bin/env stack
 {- stack script
-   --snapshot lts-22.28
+   --snapshot lts-22.43
    --package turtle
    --package "stm async"
    --package http-client,http-conduit
@@ -207,7 +207,7 @@ which makes use of the joke package
 
 ~~~haskell
 {- stack script
-   --snapshot lts-22.28
+   --snapshot lts-22.43
    --package acme-missiles
 -}
 import Acme.Missiles (launchMissiles)
@@ -218,7 +218,7 @@ main = launchMissiles
 
 The command `stack --script-no-run-compile Script.hs` then behaves as if the
 command
-`stack script --snapshot lts-22.28 --package acme-missiles --no-run --compile -- Script.hs`
+`stack script --snapshot lts-22.43 --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!
 
@@ -260,7 +260,7 @@ those curious, here is an example with
 {- stack
   runghc
   --install-ghc
-  --snapshot lts-22.28
+  --snapshot lts-22.43
   --package base
   --package turtle
   --
@@ -284,7 +284,7 @@ it. Here is an example:
 {- stack
    exec ghci
    --install-ghc
-   --snapshot lts-22.28
+   --snapshot lts-22.43
    --package turtle
 -}
 ~~~

doc/topics/stack_yaml_vs_cabal_package_file.md

@@ -64,9 +64,9 @@ requires that you have chosen a specific version for each package available.
 
 The most common means by which this set of packages is defined is via a
 snapshot provided by Stackage. For example, if you go to the page
-<https://www.stackage.org/lts-22.28>, you will see a list of 3,373 packages at
-specific version numbers. When you then specify `snapshot: lts-22.28` or,
-alternatively, `resolver: lts-22.28`, you're telling Stack to use those package
+<https://www.stackage.org/lts-22.43>, you will see a list of 3,378 packages at
+specific version numbers. When you then specify `snapshot: lts-22.43` or,
+alternatively, `resolver: lts-22.43`, you're telling Stack to use those package
 versions in resolving dependencies down to specific versions of packages.
 
 Sometimes a snapshot doesn't have all of the packages that you want. Or you want