Bump to Stackage LTS Haskell 23.17

Depends on the existing work around for: #6711.

On Windows only, for some unidentified reason, stack script can fail when using a pre-compiled package. This affects the script build-stack-installer.hs because, with LTS Haskell 23.17, syb becomes a dependency of Stack and the script sees syb as a pre-compiled package. The work around is to build the package required for that script using the same Stack configuration as used by the script.

Author: mpilgrem

.github/workflows/integration-tests.yml

@@ -47,7 +47,7 @@ jobs:
           cache-bust: "2025-02-07b"
         - os: windows-latest
           release-args: ""
-          cache-bust: "2024-05-17"
+          cache-bust: "2025-04-06"
         - os: macos-13
           release-args: ""
           cache-bust: "2024-05-17"

.gitignore

@@ -7,6 +7,7 @@ dist-newstyle/
 # Haskell Tool Stack-related
 .stack-work/
 tests/integration/tests/**/*.yaml.lock
+etc/scripts/stack.yaml.lock
 
 # Stack's GitHub workflow-related
 _release/

CONTRIBUTING.md

@@ -349,8 +349,8 @@ 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 (March 2025) the package versions are
-primarily ones in Stackage snapshot LTS Haskell 23.14 (for GHC 9.8.4) and
-`hpack-0.38.0`.
+primarily ones in Stackage snapshot LTS Haskell 23.17 (for GHC 9.8.4) and
+`hpack-0.38.1`.
 
 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

@@ -52,7 +52,7 @@ constraints:
   , contravariant ==1.5.5
   , cookie ==0.5.0
   , cryptohash-sha256 ==0.11.102.1
-  , crypton ==1.0.1
+  , crypton ==1.0.3
   , crypton-conduit ==0.2.3
   , crypton-connection ==0.4.3
   , crypton-x509 ==1.7.7
@@ -79,7 +79,7 @@ constraints:
   , file-embed ==0.0.16.0
   , filelock ==0.1.1.7
   , filepath ==1.4.301.0
-  , fsnotify ==0.4.1.0
+  , fsnotify ==0.4.2.0
   , generic-deriving ==1.14.6
   , generically ==0.1.1
   , ghc-bignum ==1.3
@@ -89,13 +89,17 @@ constraints:
   , githash ==0.1.7.0
   , hackage-security ==0.6.2.6
   , half ==0.3.2
+  , happy ==2.0.2
+  , happy-lib ==2.0.2
   , hashable ==1.4.7.0
+  , haskell-src-exts ==1.23.1
+  , haskell-src-meta ==0.8.15
   , hi-file-parser ==0.1.7.0
   , hourglass ==0.2.12
-  , hpack ==0.38.0
+  , hpack ==0.38.1
   , hpc ==0.7.0.0
   , http-api-data ==0.6.1
-  , http-client ==0.7.18
+  , http-client ==0.7.19
   , http-client-tls ==0.3.6.4
   , http-conduit ==2.3.9.1
   , http-download ==0.2.1.0
@@ -120,7 +124,7 @@ constraints:
   , mime-types ==0.1.2.0
   , mintty ==0.1.4
   , monad-control ==1.0.3.1
-  , monad-logger ==0.3.41
+  , monad-logger ==0.3.42
   , monad-loops ==0.4.3
   , mono-traversable ==1.0.21.0
   , mtl ==2.3.1
@@ -131,7 +135,7 @@ constraints:
   , network-uri ==2.6.4.2
   , old-locale ==1.0.0.7
   , old-time ==1.1.0.4
-  , open-browser ==0.2.1.0
+  , open-browser ==0.2.1.1
   , optparse-applicative ==0.18.1.0
   , optparse-simple ==0.1.1.4
   , os-string ==2.0.7
@@ -175,20 +179,26 @@ constraints:
   , stm-chans ==3.0.0.9
   , streaming-commons ==0.2.3.0
   , strict ==0.5.1
+  , string-interpolate ==0.3.4.0
+  , syb ==0.7.2.4
   , tagged ==0.8.8
   , tar ==0.6.3.0
   , tar-conduit ==0.4.1
   , tasty ==1.5.3
   , template-haskell ==2.21.0.0
   , temporary ==1.3
   , text ==2.1.1
+  , text-conversions ==0.3.1.1
   , text-iso8601 ==0.1.1
   , text-metrics ==0.3.3
   , text-short ==0.1.6
   , th-abstraction ==0.7.1.0
   , th-compat ==0.1.6
+  , th-expand-syns ==0.4.12.0
   , th-lift ==0.8.6
   , th-lift-instances ==0.1.20
+  , th-orphans ==0.13.16
+  , th-reify-many ==0.1.10
   , these ==1.2.1
   , time ==1.12.2
   , time-compat ==1.9.7
@@ -198,11 +208,12 @@ constraints:
   , transformers-compat ==0.7.2
   , typed-process ==0.2.12.0
   , unix ==2.8.6.0
-  , unix-compat ==0.7.3
+  , unix-compat ==0.7.4
   , unix-time ==0.4.16
-  , unliftio ==0.2.25.0
+  , unliftio ==0.2.25.1
   , unliftio-core ==0.2.1.0
   , unordered-containers ==0.2.20
+  , utf8-string ==1.0.2
   , uuid-types ==1.0.6
   , vault ==0.3.1.5
   , vector ==0.13.2.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-23.14/cabal.config.
+-- https://www.stackage.org/lts-23.17/cabal.config.
 --
 with-compiler: ghc-9.8.4
 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-23.14 list base unix Win32 acme-missiles pantry
+stack --snapshot lts-23.17 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.14 list base unix Win32 pantry
+stack --snapshot lts-23.17 list base unix Win32 pantry
 base-4.19.2.0
 unix-2.8.6.0
 Win32-2.13.4.0
 pantry-0.10.0
 
-stack --snapshot lts-23.14 list
+stack --snapshot lts-23.17 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.14 MyScript.hs
+stack script --snapshot lts-23.17 MyScript.hs
 ~~~
 
 An extra-dep from the package index can be added to the snapshot on the command
@@ -197,7 +197,7 @@ main = do
 can be compiled and run, with arguments, with:
 
 ~~~text
-stack --snapshot lts-23.14 script --package acme-missiles --compile MyScript.hs -- "Don't panic!" "Duck and cover!"
+stack --snapshot lts-23.17 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.
@@ -217,7 +217,7 @@ snapshot as an extra-dep. The `stack script` command is specified using Stack's
 
 ~~~haskell
 {- stack script
-   -- snapshot lts-23.14
+   -- snapshot lts-23.17
    -- extra-dep acme-missiles-0.2
    -- package acme-missiles
 -}
@@ -319,7 +319,7 @@ A Haskell source file `MyScript.hs`, as follows:
 
 ~~~haskell
 {- stack script
-   --snapshot lts-23.14
+   --snapshot lts-23.17
 -}
 
 {-# 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.14
+snapshot: lts-23.17
 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.14`
-* Stackage Nightly snapshots, e.g. `snapshot: nightly-2025-02-15`
+* LTS Haskell snapshots, e.g. `snapshot: lts-23.17`
+* Stackage Nightly snapshots, e.g. `snapshot: nightly-2025-04-05`
 * 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.14`
+        installed that version). For example, to use `snapshot: lts-23.17`
         (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.14 # Inherits GHC version and package set
+snapshot: lts-23.17 # 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.14`, but
+The following snapshot specification will be identical to `lts-23.17`, but
 instead use `ghc-9.8.3` instead of `ghc-9.8.4`:
 
 ~~~yaml
-snapshot: lts-23.14
+snapshot: lts-23.17
 compiler: ghc-9.8.3
 ~~~
 
 ### Dropping packages
 
-The following snapshot specification will be identical to `lts-23.14`, but
+The following snapshot specification will be identical to `lts-23.17`, 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.14
+snapshot: lts-23.17
 drop-packages:
 - text
 ~~~
 
 ### Hiding packages
 
-The following snapshot specification will be identical to `lts-23.14`, but the
+The following snapshot specification will be identical to `lts-23.17`, 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.14
+snapshot: lts-23.17
 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.14`, but
+The following snapshot specification will be identical to `lts-23.17`, but
 provides `-O1` as a ghc-option for `text`:
 
 ~~~yaml
-snapshot: lts-23.14
+snapshot: lts-23.17
 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.14`, but
+following snapshot specification will be identical to `lts-23.17`, but
 it enables the `developer` Cabal flag:
 
 ~~~yaml
-snapshot: lts-23.14
+snapshot: lts-23.17
 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.14 # GHC 9.8.4
+snapshot: lts-23.17 # 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.14 # GHC 9.8.4
+snapshot: lts-23.17 # GHC 9.8.4
 ~~~
 
 This example project can be built with Stack in the normal way (`stack build`),