Haskell Stack च्या जुन्या आवृत्त्या डाउनलोड करा

See https://haskellstack.org/ for installation and upgrade instructions.
Changes since v3.9.3:
Major changes:
- On 64-bit Windows, the default msys-environment configuration option is now CLANG64, rather than MINGW64 (which remains an option). The MSYS2 project deprecated the latter environment on 15 March 2026. The GHC project has used the former toolchain from GHC 9.4.1. No default is provided for 32-bit Windows, rather than MINGW32 (which remains an option). The MSYS2 project ceased to actively support it on 17 May 2020. 32-bit Windows is not supported by the GHC project from GHC 8.12.
Behavior changes:
- Stack's default Nix integration now includes the cacert Nix package, in order to support Stack's use of crypton-x509-system >= 1.6.8.
- Following a change to the Stackage project's server API, the default value of the urls key includes recent-snapshots: https://stackage.org/api/v1/snapshots.
- The --[no-]keep-ghc-rts flag of Stack's config env command is now enabled by default, consistent with Stack's exec command.
- On Windows, in the Stack environment, the MSYS2 usr/local/bin directory (if it exists) is now searched before the MSYS2 usr/bin directory, rather than after.
Other enhancements:
- Bump to Hpack 0.39.6.
- Experimental: Add flag --[no-]semaphore (default: disabled) to Stack's build command, to allow GHC to use a system semaphore to perform compilation in parallel when possible. Supported, by default, by GHC 9.10.1 or later. The option is considered experiemental because, on Linux only, musl and non-musl semaphores are incompatible.
- Add option --reach <packages> to Stack's dot and ls dependencies commands, to prune packages that cannot reach any of the specified packages in the dependency graph.
- Add option --test-suite-timeout-grace=SECONDS to Stack's build command to request termination of a timed-out test suite process and, after the specified grace period, force termination. Used together with the existing --test-suite-timeout=SECONDS option.
- In YAML configuration files, the recent-snapshots key is introduced (under the urls key), to specify the URL used by Stack's ls snapshots remote command.
- In YAML configuration files (stack.yaml and config.yaml), an !include <file path> directive is now supported. This allows common configuration to be shared across multiple files. For example, a project that maintains multiple project-level configuration files for testing against different snapshots can use !include to avoid duplicating shared settings.
- Stack's config set command raises an error if the target configuration file excludes the key being set and includes an !include directive.
- Stack's config set snapshot command now works with other snapshot values in addition to snapshot synonymns.
- Add Stack's config compiler-tools command to create (when applicable) the compiler tools directory for the specified compiler version (implies Stack's config build-files command).
Bug fixes:
- Stack's dot and ls dependencies commands no longer prune a package with dependencies only because all its direct dependencies are to be pruned.
- After March 2026, Hackage requires Stack's user agent to be set when applying digest authentication to a request. Stack's upload command now does that, re-establishing authentication by Hackage username and password.
- Stack 3.9.3 and earlier fail to construct a build plan if project package A depends on project package B and package B's executables (only) depend on package A and the name of A is before that of B, alphabetically. That bug is fixed.
- Stack's config set commands will recreate the global-project directory contents, if Stack needs to consult its project-level configuration file and there is no file.
- The output of Stack's path --bin-path command is now consistent with the Stack environment in Stack's exec command and includes the bin directory of Stack's local install root directory.
- Stack now builds packages that depend directly on packages with the same name as a su

See https://haskellstack.org/ for installation and upgrade instructions.
Release notes:
- This release fixes a potential bug for users of Stack's Docker integration.
Changes since v3.9.1:
Other enhancements:
- The resolver synonym for snapshot, informally deprecated from Stack 3.1.1, is formally deprecated in online and in-app documentation.
Bug fixes:
- Stack's Docker integration supports Docker client versions 29.0.0 and greater.
Thanks to all our contributors for this release:
- Jens Petersen
- Mike Pilgrem
- Olivier Benz

See https://haskellstack.org/ for installation and upgrade instructions.
Changes since v3.7.1:
Behavior changes:
- Where applicable and Stack supports the GHC version, only the wired-in packages of the actual version of GHC used are treated as wired-in packages.
- Stack now recognises ghc-internal as a GHC wired-in package.
- The configuration option package-index has a new default value: the keyids key lists the keys of the Hackage root key holders applicable from 2025-07-24.
- Stack's dot command now treats --depth the same way as the ls dependencies command, so that the nodes of stack dot --external --depth 0 are the same as the packages listed by stack ls dependencies --depth 0.
- When building GHC from source, on Windows, the default Hadrian build target is reloc-binary-dist and the default path to the GHC built by Hadrian is _build/reloc-bindist.
- Stack's haddock command no longer requires a package to have a main library that exposes modules.
- On Windows, the path segment platform\hash\ghc version, under .stack-work\install and .stack-work\hoogle, is hashed only once, rather than twice.
Other enhancements:
- Bump to Hpack 0.39.1.
- Consider GHC 9.14 to be a tested compiler and remove warnings.
- Consider Cabal 3.16 to be a tested library and remove warnings.
- From GHC 9.12.1, base is not a GHC wired-in package. In configuration files, the notify-if-base-not-boot key is introduced, to allow the exisitng notification to be muted if unwanted when using such GHC versions.
- Add flag --[no-]omit-this (default: disabled) to Stack's clean command to omit directories currently in use from cleaning (when --full is not specified).
- Add option -w as synonym for --stack-yaml.
- stack new now allows codeberg: as a service for template downloads
- In YAML configuration files, the compiler-target and compiler-bindist-path keys are introduced to allow, when building GHC from source, the Hadrian build target and Hadrian path to the built GHC to be specified.
Bug fixes:
- --PROG-option=<argument> passes --PROG-option=<argument> (and not --PROG-option="<argument>") to Cabal (the library).
- The message S-7151 now presents as an error, with advice, and not as a bug.
- Stack's dot command now uses a box to identify all GHC wired-in packages, not just those with no dependencies (being only rts).
- Stack's dot command now gives all nodes with no dependencies in the graph the maximum rank, not just those nodes with no relevant dependencies at all (being only rts, when --external is specified).
- Improved error messages for S-4634 and S-8215.
- Improved in-app help for the --hpack-force flag.
Thanks to all our contributors for this release:
- Alexey Kotlyarov
- Dino Morelli
- Jens Petersen
- Lauren Yim
- Mike Pilgrem
- Olivier Benz
- Simon Hengel
- Wolfram Kahl

See https://haskellstack.org/ for installation and upgrade instructions.
Changes since v3.5.1:
Other enhancements:
- Bump to Hpack 0.38.1.
- The --extra-dep option of Stack's script command now accepts a YAML value specifying any immutable extra-dep. Previously only an extra-dep in the package index that could be specified by a YAML string (for example, acme-missiles-0.3@rev:0) was accepted.
Bug fixes:
- stack script --package <pkg-name> now uses GHC's -package-id option to expose the installed package, rather than GHC's -package option. For packages with public sub-libraries, -package <pkg> can expose an installed package other than one listed by ghc-pkg list <pkg>.
- Work around ghc-pkg bug where, on Windows only, it cannot register a package into a package database that is also listed in the GHC_PACKAGE_PATH environment variable. In previous versions of Stack, this affected stack script when copying a pre-compiled package from another package database.
- On Windows, when decompressing, and extracting tools, from archive files, Stack uses the system temporary directory, rather than the root of the destination drive, if the former is on the destination drive.
Thanks to all our contributors for this release:
- Max Ulidtko
- Mike Pilgrem
- Olivier Benz
- Simon Hengel

See https://haskellstack.org/ for installation and upgrade instructions.
Changes since v3.3.1:
Behavior changes:
- Stack will also warn (message S-8432) if there is any non-ISO/IEC 8859-1 (Latin-1) character in Stack's 'programs' path, as hsc2hs does not work if there is such a character in the path to its default template template-hsc.h.
- Stack customizes setup using Cabal, so if a setup-depends field does not mention it as a dependency, Stack warns and adds the GHC boot package as a dependency. Previously, Stack would not do so but only warn that build errors were likely.
Other enhancements:
- Bump to Hpack 0.38.0.
- In YAML configuration files, the install-msys key is introduced, to enable or disable the download and installation of Stack-supplied MSYS2 when necessary (subject to skip-msys: false). The default is the same as the install-ghc setting (including if that is set at the command line). Consequently, the default behaviour of Stack is unaffected.
- Add the stack config set install-msys command to configure the install-msys option in YAML configuration files.
- Option allow-newer-deps is no longer classified as experimental in documentation.
- stack sdist and stack upload report the version of Cabal (the library) being used to check packages.
- Add the stack config build-files command to generate (when applicable) a Cabal file from a package description in the Hpack format and/or a lock file for Stack's project-level configuration, without taking any other build steps.
Thanks to all our contributors for this release:
- Mike Pilgrem
- Olivier Benz

See https://haskellstack.org/ for installation and upgrade instructions.Changes since v3.1.1:Behavior changes:
- Stack interprets consecutive line ends in the value of the user-message project-specific configuration option as a single blank line. Previously all line ends were interpreted as white space.
- Stack no longer supports Docker versions before Docker 1.9.1 and, consequently, if a Docker container is not being run 'detached', its standard input channel will always be kept open. (Before Docker 1.9.1 the use of an interactive container could hang in certain circumstances.)
- On Windows, Stack will always warn (message S-8432) if there is a space character in Stack's 'programs' path, as GHC 9.4.1 and later do not work if there is a space in the path to the ghc executable. S-8432 now presents as a warning and not an error.
- Stack respects the --no-run-tests and --no-run-benchmarks flags when determining build actions. Previously Stack respected the flags when executing the run test suites or run benchmarks actions for each targeted project package.
Other enhancements:
- Consider GHC 9.10 to be a tested compiler and remove warnings.
- Consider Cabal 3.12 to be a tested library and remove warnings.
- Add flags --run-tests and --run-benchmarks (the existing defaults) to Stack's build command, which take precedence over the existing no-run-tests and no-run-benchmarks configuration options, respectively.
- In configuration files, the notify-if-no-run-tests and notify-if-no-run-benchmarks keys are introduced, to allow the exisitng notification to be muted if unwanted.
Bug fixes:
- Stack's in-app messages refer to https://haskellstack.org as currently structured. (Most URLs in older Stack versions are redirected.)
- Stack's upgrade command only treats the current running Stack executable as 'stack' if the executable file is named stack or, on Windows, stack.exe. Previously only how it was invoked was considered.
- stack test --no-run-tests --dry-run no longer reports that Stack would test project packages with test suites and stack bench --no-run-benchmarks --dry-run no longer reports that Stack would benchmark project packages with benchmarks.
- StackSetupShim compiles with Cabal >= 3.14.0.0.
Thanks to all our contributors for this release:
- Andrew Nguyen
- Luka Leer
- Mike Pilgrem
- Olivier Benz

See https://haskellstack.org/ for installation and upgrade instructions.Release notes:
- The change in major version from 2.x to 3.1 marks the dropping of support for versions of GHC before 8.4, deprecated in Stack 2.15.1.
Changes since v2.15.7:Behavior changes:
- Stack uses the version of the Cabal package that comes with the specified version of GHC. Stack no longer supports such Cabal versions before 2.2, which came with versions of GHC before 8.4. Consequently, the init command will not try LTS Haskell before 12.0.
- The init command initialises stack.yaml with a snapshot key rather than a resolver key.
- After installing GHC or another tool, Stack deletes the archive file which provided the tool.
- Remove hidden flag --skip-intermediate-deps, effectively deprecated since Stack 1.3.0, from ghci and repl commands.
- The haddock --haddock-for-hackage command only seeks to create an archive of the <package_version>-docs directory for build targets and if flags excluding the building of project packages are not set.
- The predecessor of configuration option package-index, package-indices (deprecated in Stack 2.9.3) has been removed as an alternative option.
- If a build target is a package identifier, and the package version is not in the snapshot or the package index, Stack will report an error when the target is parsed. Previously, if another version of the package was in the snapshot, Stack would construct the build plan with that other version or, if it was not, Stack would defer an error to the construction of the build plan.
- The list command, with a specified snapshot and package, also reports the version of the package included indirectly in the snapshot (as a boot package of the compiler specified by the snapshot).
- stack build --flag *:[-]<flag_name> now only applies the flag setting to packages for which the Cabal flag is defined, as opposed to all packages.
- On Unix-like operating systems, drop support for /etc/stack/config, deprecated in Stack 0.1.6.0.
- Drop support for, in the Stack root, directory global and file stack.yaml, both deprecated in Stack 0.1.6.0.
Other enhancements:
- Bump to Hpack 0.37.0.
- In YAML configuration files, the msys-environment key is introduced to allow, on Windows, the MSYS2 environment to be specified. The default environment is still MINGW64 on 64-bit Windows and MINGW32 on 32-bit Windows.
- In YAML configuration files, the default-init-snapshot key is introduced to allow a default snapshot to be specified for use with the stack init command, as if it had been specified at the command line.
- Add flags --haddock-executables, --haddock-tests and --haddock-benchmarks to Stack's build command (including the haddock synonym for build --haddock) to enable also building Haddock documentation for executables, test suites and benchmarks. Due to a bug in Cabal (the library), Stack will ignore the flags with a warning for GHC versions before 9.4.
- Add flag --[no-]save-hackage-creds to Stack's upload command, which takes precedence over the existing save-hackage-creds configuration option.
- In YAML configuration files, the global-hints-location key is introduced to allow the location of the global hints YAML specification file to be specified.
- By default, Hpack 0.20.0 or later will decline to overwrite a Cabal file that was modified manually. In YAML configuration files, the hpack-force key is introduced to allow Hpack to overwrite such a Cabal file. The corresponding --hpack-force flag is also added.
- Add the stack config set recommend-stack-upgrade command to configure whether or not Stack should notify the user if it identifes a new version of Stack is available in YAML configuration files.
- Add the ls globals command to list all global packages for the version of GHC specified by the snapshot.
- Add stack -h (equivalent to stack --help).
- In YAML configuration files, the file-watch-hook key is introduced to allow --file-watch post-processing to be customised with a executable or 

See https://haskellstack.org/ for installation and upgrade instructions.Release notes:- This release fixes potential bugs.
- The hash that Stack uses to distinguish one build plan from another has changed for plans that set (as opposed to unset) manually Cabal flags for immutable dependencies. This will cause Stack to rebuild dependencies for such plans.
Changes since v2.15.5:Major changes:- Stack 2.15.5 and earlier cannot build with Cabal (the library) version 3.12.0.0. Stack can now build with that Cabal version.
Behavior changes:- Stack's StackSetupShim executable, when called with repl and stack-initial-build-steps, no longer uses Cabal's replHook to apply initialBuildSteps but takes a more direct approach.
Bug fixes:- Fix a regression introduced in Stack 2.15.1 that caused a 'no operation' stack build to be slower than previously.
- The hashes that Stack uses to distinguish one build plan from another now include the Cabal flags for immutable dependencies set manually. Previously, in error, only such flags that were unset manually were included.
Thanks to all our contributors for this release:- Jörg Thalheim
- Mike Pilgrem

- Add flag --[no-]-only-local-bin to Stack's upgrade command for a binary upgrade.
If the Stack executable is my-stack, the default is my-stack upgrade --only-local-bin where previously it was, effectively, my-stack upgrade --no-only-local-bin.
If the Stack executable is stack, the default is stack upgrade --no-only-local-bin, the same behaviour as previously.
- Use $XDG_CACHE_HOME/stack/ghci-script, rather than <temp>/haskell-stack-ghci (where <temp> is the directory yielded by the temporary package's System.
IO.Temp.getCanonicalTemporaryDirectory), as the base location for GHCi script files generated by stack ghci or stack repl. See #5203
- Drop support for Cabal versions before 1.22 and, consequently, GHC versions before 7.10.
- stack ghci and stack repl now take into account the values of default-language keys in Cabal files, like they take into account the values of default-extensions keys.
- Removed --ghc-paths, --global-stack-root and --local-bin-path flags for stack path, deprecated in Stack 1.1.0 in favour of --programs, --stack-root and local-bin respectively.
- On Windows, stack upgrade always renames the file of the running Stack executable (adding extension .old) before attempting to write to the original file name.
- On Windows, stack upgrade does not offer sudo command alternatives if attempting to write to the original file name of the running Stack exectuable results in a 'Permission' error.
- Add options of the form --PROG-option=<argument> to stack build, where PROG is a program recognised by the Cabal library and one of alex, ar, c2hs, cpphs, gcc, greencard, happy, hsc2hs, hscolour, ld, pkg-config, strip and tar.
If Cabal uses the program during the configuration step, the argument is passed to it.
- By default all --PROG-option options are applied to all local packages.
This behaviour can be changed with new configuration option apply-prog-options.
- Add flag --[no-]use-root to stack script (default disabled).
Used with --compile or --optimize, when enabled all compilation outputs (including the executable) are written to a script-specific location in the scripts directory of the Stack root rather than the script's directory, avoiding clutter of the latter directory.
- Better error message if the value of the STACK_WORK environment variable or --work-dir option is not a valid relative path.
- Stack will use the value of the GH_TOKEN, or GITHUB_TOKEN, environment variable as credentials to authenticate its GitHub REST API requests.
- stack uninstall also shows how to uninstall Stack-supplied tools.
- Fix incorrect warning if allow-newer-deps are specified but allow-newer is false.
See #6068.
- stack build with --file-watch or --file-watch-poll outputs 'pretty' error messages, as intended. See #5978.
- stack build unregisters any local packages for the sub libraries of a local package that is to be unregistered. See #6046.
- The warning that sublibrary dependency is not supported is no longer triggered by internal libraries.
- Chris Wendt
- Illia Bobyr
- Jens Petersen
- Max Taldykin
- MaxHearnden
- Mike Pilgrem
- Phil de Joux
- theophilebatoz