Bump snapshot

Author: mpilgrem

cabal.config

@@ -9,7 +9,7 @@ constraints:
   , aeson ==2.1.2.1
   , aeson-warning-parser ==0.1.1
   , annotated-wl-pprint ==0.7.0
-  , ansi-terminal ==1.0
+  , ansi-terminal ==1.0.2
   , ansi-terminal-types ==0.11.5
   , appar ==0.1.8
   , array ==0.5.5.0
@@ -84,15 +84,15 @@ constraints:
   , ghc-boot-th ==9.6.3
   , ghc-prim ==0.10.0
   , githash ==0.1.7.0
-  , hackage-security ==0.6.2.3
+  , hackage-security ==0.6.2.4
   , hashable ==1.4.3.0
   , hi-file-parser ==0.1.6.0
   , hinotify ==0.4.1
   , hourglass ==0.2.12
   , hpack ==0.36.0
   , hpc ==0.6.2.0
   , http-api-data ==0.5.1
-  , http-client ==0.7.15
+  , http-client ==0.7.16
   , http-client-tls ==0.3.6.3
   , http-conduit ==2.3.8.3
   , http-download ==0.2.1.0
@@ -161,7 +161,7 @@ constraints:
   , semigroupoids ==6.0.0.1
   , silently ==1.2.5.3
   , socks ==0.6.1
-  , split ==0.2.4
+  , split ==0.2.5
   , splitmix ==0.1.0.5
   , stack ==2.14.0
   , static-bytes ==0.1.0
@@ -194,12 +194,12 @@ constraints:
   , unix-time ==0.4.11
   , unliftio ==0.2.25.0
   , unliftio-core ==0.2.1.0
-  , unordered-containers ==0.2.19.1
+  , unordered-containers ==0.2.20
   , uuid-types ==1.0.5.1
   , vault ==0.3.1.5
   , vector ==0.13.1.0
   , vector-algorithms ==0.9.0.1
-  , vector-stream ==0.1.0.0
+  , vector-stream ==0.1.0.1
   , witherable ==0.4.2
   , yaml ==0.11.11.2
   , zip-archive ==0.4.3

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.0/cabal.config.
+-- https://www.stackage.org/lts-22.6/cabal.config.
 --
 with-compiler: ghc-9.6.3
 import: cabal.config

doc/GUIDE.md

@@ -255,7 +255,7 @@ packages:
 
 The value of the `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.0](https://www.stackage.org/lts-22.0), which
+says to use [LTS Haskell 22.6](https://www.stackage.org/lts-22.6), which
 implies GHC 9.6.3 (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.
@@ -503,7 +503,7 @@ also known as *snapshots*. We mentioned the LTS resolvers, and you can get quite
 a bit of information about it at
 [https://www.stackage.org/lts](https://www.stackage.org/lts), including:
 
-* The appropriate resolver value (`resolver: lts-22.0`, as is currently the
+* The appropriate resolver value (`resolver: lts-22.6`, as is currently the
   latest LTS)
 * The GHC version used
 * A full list of all packages available in this snapshot
@@ -522,7 +522,7 @@ towards by default as well).
 
 ## Resolvers and changing your compiler version
 
-Let's explore package sets a bit further. Instead of `lts-22.0`, let's change
+Let's explore package sets a bit further. Instead of `lts-22.6`, let's change
 our `stack.yaml` file to use the
 [latest nightly](https://www.stackage.org/nightly). Right now, this is currently
 2023-09-24 - please see the resolver from the link above to get the latest.
@@ -1340,7 +1340,7 @@ yields output like:
 
 ~~~text
 Run from outside a project, using implicit global project config
-Using latest snapshot resolver: lts-22.0
+Using latest snapshot resolver: lts-22.6
 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,7 +75,7 @@ enabled). For further information about these options, see the `install-ghc`
 
 For this workaround to work, each time that a resolver 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 `resolver: lts-22.0`
+not already installed that version). For example, to use `resolver: lts-22.6`
 (GHC 9.6.3), the command `ghcup install ghc 9.6.3` must have been used to
 install GHC 9.6.3. That may be a minor inconvenience for some people, as one the
 primary benefits of Stack over other Haskell build tools has been that Stack

doc/custom_snapshot.md

@@ -17,7 +17,7 @@ available in snapshots to ensure reproducibility.
     snapshot specification.
 
 ~~~yaml
-resolver: lts-22.0 # Inherits GHC version and package set
+resolver: lts-22.6 # Inherits GHC version and package set
 compiler: ghc-9.6.2 # Overwrites GHC version in the resolver, optional
 
 # Additional packages, follows extra-deps syntax
@@ -61,35 +61,35 @@ custom snapshot, due to Stack sharing snapshot packages whenever possible.
 
 ### Overriding the compiler
 
-The following snapshot specification will be identical to `lts-22.0`, but
+The following snapshot specification will be identical to `lts-22.6`, but
 instead use `ghc-9.6.2` instead of `ghc-9.6.3`:
 
 ~~~yaml
-resolver: lts-22.0
+resolver: lts-22.6
 compiler: ghc-9.6.2
 ~~~
 
 ### Dropping packages
 
-The following snapshot specification will be identical to `lts-22.0`, but
+The following snapshot specification will be identical to `lts-22.6`, 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
-resolver: lts-22.0
+resolver: lts-22.6
 drop-packages:
 - text
 ~~~
 
 ### Hiding packages
 
-The following snapshot specification will be identical to `lts-22.0`, but the
+The following snapshot specification will be identical to `lts-22.6`, but the
 `text` package will be hidden when registering. This will affect, for example,
 the import parser in the script command.
 
 ~~~yaml
-resolver: lts-22.0
+resolver: lts-22.6
 hidden:
 - text
 ~~~
@@ -99,11 +99,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.0`, but
+The following snapshot specification will be identical to `lts-22.6`, but
 provides `-O1` as a ghc-option for `text`:
 
 ~~~yaml
-resolver: lts-22.0
+resolver: lts-22.6
 packages:
 - text-2.0.2
 ghc-options:
@@ -122,11 +122,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.0`, but
+following snapshot specification will be identical to `lts-22.6`, but
 it enables the `developer` Cabal flag:
 
 ~~~yaml
-resolver: lts-22.0
+resolver: lts-22.6
 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 _resolver_. This may be something like `lts-22.0`, which is from
+the _resolver_. This may be something like `lts-22.6`, which is from
 [Stackage](https://www.stackage.org/). The [user's guide](GUIDE.md) discusses
 the resolver 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
-resolver: lts-22.0
+resolver: lts-22.6
 packages:
 - .
 extra-deps:
@@ -91,7 +91,7 @@ Add it to the
 directory where your `stack.yaml` file lives, e.g.
 
 ~~~yaml
-resolver: lts-22.0
+resolver: lts-22.6
 packages:
 - .
 extra-deps:

doc/list_command.md

@@ -44,17 +44,17 @@ Error: [S-4926]
          pantry, pretty, pasty, xattr, alloy, para, pappy, alure, polar and
          factory.
 
-stack --resolver lts-22.0 list base unix Win32 acme-missiles pantry
+stack --resolver lts-22.6 list base unix Win32 acme-missiles pantry
 Error: [S-4926]
        * Package does not appear in snapshot: base.
        * Package does not appear in snapshot: unix.
        * Package does not appear in snapshot: Win32.
        * Package does not appear in snapshot: acme-missiles.
 
-stack --resolver lts-22.0 list pantry
+stack --resolver lts-22.6 list pantry
 pantry-0.9.3.1
 
-stack --resolver lts-22.0 list
+stack --resolver lts-22.6 list
 AC-Angle-1.0
 ALUT-2.4.0.3
 ...

doc/script_command.md

@@ -18,7 +18,7 @@ configuration files (global and project-level). A snapshot must be specified on
 the command line (with the `--resolver` option). For example:
 
 ~~~text
-stack script --resolver lts-22.0 MyScript.hs
+stack script --resolver lts-22.6 MyScript.hs
 ~~~
 
 The `stack script` command behaves as if the `--install-ghc` flag had been
@@ -100,7 +100,7 @@ main = do
 can be compiled and run, with arguments, with:
 
 ~~~text
-stack --resolver lts-22.0 script --package acme-missiles --compile MyScript.hs -- "Don't panic!" "Duck and cover!"
+stack --resolver lts-22.6 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 --resolver lts-22.0 --package turtle
+-- stack script --resolver lts-22.6 --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` command with the options of a
-LTS Haskell 22.0 snapshot (`--resolver lts-22.0`) and ensuring the
+LTS Haskell 22.6 snapshot (`--resolver lts-22.6`) 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.0` provides `turtle-1.6.2`).
+snapshot (`lts-22.6` 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
-   --resolver lts-22.0
+   --resolver lts-22.6
    --
    +RTS -s -RTS
 -}
@@ -132,7 +132,7 @@ main = do
 is equivalent to the following command at the command line:
 
 ~~~text
-stack script --resolver lts-22.0 -- MyScript.hs arg1 arg2 +RTS -s -RTS
+stack script --resolver lts-22.6 -- MyScript.hs arg1 arg2 +RTS -s -RTS
 ~~~
 
 where `+RTS -s -RTS` are some of GHC's
@@ -161,7 +161,7 @@ space separated list. For example:
 ~~~haskell
 #!/usr/bin/env stack
 {- stack script
-   --resolver lts-22.0
+   --resolver lts-22.6
    --package turtle
    --package "stm async"
    --package http-client,http-conduit
@@ -191,7 +191,7 @@ which makes use of the joke package
 
 ~~~haskell
 {- stack script
-   --resolver lts-22.0
+   --resolver lts-22.6
    --package acme-missiles
 -}
 import Acme.Missiles (launchMissiles)
@@ -202,7 +202,7 @@ main = launchMissiles
 
 The command `stack --script-no-run-compile Script.hs` then behaves as if the
 command
-`stack script --resolver lts-22.0 --package acme-missiles --no-run --compile -- Script.hs`
+`stack script --resolver lts-22.6 --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!
 
@@ -239,7 +239,7 @@ example with `runghc`:
 {- stack
   runghc
   --install-ghc
-  --resolver lts-22.0
+  --resolver lts-22.6
   --package base
   --package turtle
   --
@@ -262,7 +262,7 @@ it. Here is an example:
 {- stack
    exec ghci
    --install-ghc
-   --resolver lts-22.0
+   --resolver lts-22.6
    --package turtle
 -}
 ~~~

doc/stack_yaml_vs_cabal_package_file.md

@@ -64,8 +64,8 @@ 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.0>, you will see a list of 3,341 packages at
-specific version numbers. When you then specify `resolver: lts-22.0`, you're
+<https://www.stackage.org/lts-22.6>, you will see a list of 3,341 packages at
+specific version numbers. When you then specify `resolver: lts-22.6`, you're
 telling Stack to use those package versions in resolving dependencies down to
 specific versions of packages.