All Versions
56
Latest Version
Avg Release Cycle
91 days
Latest Release
-

Changelog History
Page 1

  • v2.7.5 Changes

    πŸ”„ Changes since v2.7.3:

    Behavior changes:

    • πŸ‘€ Cloning git repositories isn't per sub-directory anymore, see #5411

    Other enhancements:

    • 🍎 stack setup supports installing GHC for macOS aarch64 (M1)

    • πŸ‘ stack upload supports authentication with a Hackage API key (via HACKAGE_KEY environment variable).

    πŸ› Bug fixes:

    • 🏁 Ensure that extra-path works for case-insensitive PATHs on Windows. See rio#237
    • πŸ›  Fix handling of overwritten ghc and ghc-pkg locations. #5597
    • πŸ›  Fix failure to find package when a dependency is shared between projects. #5680
    • πŸ“¦ stack ghci now uses package flags in stack.yaml #5434

  • v2.7.3 Changes

    πŸ”„ Changes since v2.7.1:

    Other enhancements:

    • ⬆️ stack upgrade will download from haskellstack.org before trying github.com. See #5288
    • ⬆️ stack upgrade makes less assumptions about archive format. See #5288
    • βž• Add a --no-run flag to the script command when compiling.

    πŸ› Bug fixes:

    • πŸ— GHC source builds work properly for recent GHC versions again. See #5528
    • πŸ‘ stack setup always looks for the unpacked directory name to support different tar file naming conventions. See #5545
    • ⬆️ Bump pantry version for better OS support. See pantry#33
    • πŸ— When building the sanity check for a new GHC install, make sure to clear GHC_PACKAGE_PATH.
    • Specifying GHC RTS flags in the stack.yaml no longer fails with an error. #5568
    • stack setup will look in sandboxed directories for executables, not relying on `findExecutables. See GHC issue 20074
    • Track changes to setup-config properly to avoid reconfiguring on every change. See #5578
    • πŸ“¦ stack ghci now uses package flags in stack.yaml #5434

  • v2.7.1 Changes

    πŸ”„ Changes since v2.5.1.1:

    Behavior changes:

    • stack repl now always warns about GHCi problems with loading multiple packages. It also sets now proper working directory when invoked with one package. See #5421

    • custom-setup dependencies are now properly initialized for stack dist. This makes explicit-setup-deps no longer required and that option was removed. See #4006

    Other enhancements:

    • Nix integration now passes ghcVersion (in addition to existing ghc) to shell-file as an identifier that can be looked up in a compiler attribute set.

    • Nix integration now allows Nix integration if the user is ready in nix-shell. This gets rid of "In Nix shell but reExecL is False" error.

    • πŸ“¦ stack list is a new command to list package versions in a snapshot. See #5431

    • 🚚 Consider GHC 9.0 a tested compiler and remove warnings.

    • πŸ”§ custom-preprocessor-extensions is a new configuration option for allowing stack to be aware of any custom preprocessors you have added to Setup.hs. See #3491

    • βž• Added --candidate flag to upload command to upload a package candidate rather than publishing the package.

    • Error output using --no-interleaved-output no longer prepends indentating whitespace. This allows emacs compilation-mode and vim quickfix to locate and track errors. See #5523

    πŸ› Bug fixes:

    • 0️⃣ stack new now suppports branches other than master as default for GitHub repositories. See #5422

    • πŸ‘€ Ignore all errors from hi-file-parser. See #5445 and #5486.

    • πŸ‘Œ Support basic auth in package-indices. See #5509.

    • βž• Add support for parsing .hi. files from GHC 8.10 and 9.0. See hi-file-parser#2.

  • v2.5.1 Changes

    October 15, 2020

    ⬆️ See https://haskellstack.org/ for installation and upgrade instructions.

    πŸ”„ Changes since v2.3.3

    Major changes:

    • βž• Add the snapshot-location-base yaml configuration option, which allows to
      πŸ”§ override the default location of snapshot configuration files. This option
      affects how snapshot synonyms (LTS/Nightly) are expanded to URLs by the
      pantry library.
    • 🐳 docker-network configuration key added to override docker --net arg

    Behavior changes:

    • File watching now takes into account specified targets, old behavior could
      βͺ be restored using the new flag --watch-all
      #5310

    Other enhancements:

    • stack ls dependencies json now includes fields sha256 and size for
      dependencies of type archive in location.
      #5280
    • πŸ— Build failures now show a hint to scroll up to the corresponding section
      #5279
    • πŸ’… Customisable output styles (see stack --help and the --stack-colors
      option, and stack ls stack-colors --help) now include info, debug,
      other-level, secondary and highlight, used with verbose output.

    πŸ› Bug fixes:

    • πŸ›  Fix stack test --coverage when using Cabal 3
    • stack new now generates PascalCase'd module name correctly.
      #5376
    • πŸ— Connection issues to Casa server no longer cause builds to failure. Casa acts
      πŸš‘ only as an optimizing cache layer, not a critical piece of infrastructure.
    • πŸ›  Fix modified time busting caches by always calculating sha256 digest during
      πŸ— the build process.
      #5125

    πŸš€ Thanks to all our contributors for this release:

    • Andrea Condoluci
    • Andreas Herrmann
    • Andres Schmois
    • Ariel D. Moya Sequeira
    • Brandon Chinn
    • Cheah Jer Fei
    • DerpyCrabs
    • Emanuel Borsboom
    • Felix Yan
    • Jannik Theiß
    • Jens Petersen
    • Junji Hashimoto
    • Kirill Zaborsky
    • Michael Snoyman
    • Mihai Maruseac
    • Mike Pilgrem
    • Niklas HambΓΌchen
    • OndΕ™ej SlΓ‘mečka
    • Piper McCorkle
    • Thomas Lopatic
    • tomjaguarpaw

  • v2.5.1.1 Changes

    πŸš€ Hackage-only release:

    • πŸ‘Œ Support build with persistent-2.11.x and optparse-applicative-0.16.x

  • v2.5.0.1 Changes

    September 25, 2020

    Changes since v2.3.3

    Major changes:

    • βž• Add the snapshot-location-base yaml configuration option, which allows to
      πŸ”§ override the default location of snapshot configuration files. This option
      affects how snapshot synonyms (LTS/Nightly) are expanded to URLs by the
      pantry library.
    • 🐳 docker-network configuration key added to overwrite docker --net arg

    Behavior changes:

    • File watching now takes into account specified targets, old behavior could
      βͺ be restored using the new flag --watch-all
      #5310

    Other enhancements:

    • stack ls dependencies json now includes fields sha256 and size for
      dependencies of type archive in location.
      #5280
    • πŸ— Build failures now show a hint to scroll up to the corresponding section
      #5279
    • πŸ’… Customisable output styles (see stack --help and the --stack-colors
      option, and stack ls stack-colors --help) now include info, debug,
      other-level, secondary and highlight, used with verbose output.

    πŸ› Bug fixes:

    • πŸ›  Fix stack test --coverage when using Cabal 3
    • stack new now generates PascalCase'd module name correctly.
      #5376
    • πŸ— Connection issues to Casa server no longer cause builds to failure. Casa acts
      πŸš‘ only as an optimizing cache layer, not a critical piece of infrastructure.
    • πŸ›  Fix modified time busting caches by always calculating sha256 digest during
      πŸ— the build process.
      #5125

  • v2.3.3 Changes

    August 05, 2020

    πŸ”„ Changes since v2.3.1

    Other enhancements:

    • βž• Add the stack-developer-mode flag
    • πŸ’… Customisable output styles (see stack --help and the --stack-colors option, and stack ls stack-colors --help) now include info, debug, other-level, secondary and highlight, used with verbose output.

    πŸ› Bug fixes:

    • 🐳 When using the STACK_YAML env var with Docker, make the path absolute.
    • πŸ›  Fix the problem of stack repl foo:test:bar failing without a project build before that. See #5213
    • πŸ›  Fix stack sdist introducing unneded sublibrary syntax when using pvp-bounds. See #5289
    • πŸ›  Fix modified time busting caches by always calculating sha256 digest during the build process. #5125

  • v2.3.1 Changes

    April 29, 2020

    ⬆️ See https://haskellstack.org/ for installation and upgrade instructions.

    πŸš€ Release notes:

    πŸš€ We have reduced the number of platforms that we support with binary releases.
    πŸš€ The reason behind this is that we've been slowed down in our release process
    πŸ— until now with issues trying to build binaries for less common platforms. In
    πŸ‘ order to make sure we can address issues more quickly (like supporting new
    πŸ‘ GHC versions), we're limiting support from the Stack team to:

    • Linux 64-bit (static)
    • macOS
    • Windows 64-bit

    If others want to provide additional binaries, we will definitely be happy
    πŸ‘· for the support. But since our CI system is currently able to produce these
    πŸš€ three bindists only, that's what we will be providing with the next release.

    🐧 Since we no longer have dynamically linked Linux binaries, we are removing
    🐧 removing the -static suffix from the static Linux binaries. If you have
    ⚑️ scripts to download the latest stable Linux binary, update them to use
    🐧 linux-x86_64 instead of linux-x86_64-static (if you are already using the
    πŸš€ former, nothing needs to change). For this release, both are supported, but
    πŸš€ the next release will no longer have the -static variant.

    πŸ—„ We are also deprecating the download links at https://stackage.org/stack.
    πŸ‘€ See this page for the current installation instructions:
    https://docs.haskellstack.org/en/stable/install_and_upgrade/.

    βœ… These are the canonical locations to download the latest stable binaries
    πŸ‘ from, and will continue to be supported going forward:

    As always, binaries for specific versions are available from the Github
    πŸš€ releases: https://github.com/commercialhaskell/stack/releases.

    πŸ”„ Changes since v2.1.3.1

    Major changes:

    πŸ”§ setup-info-locations yaml configuration now allows overwriting the default locations of stack-setup-2.yaml.
    #5031
    #2983
    #2913

    πŸ”§ The setup-info configuration key now allows overwriting parts of the default setup-info

    πŸ— The --setup-info-yaml command line flag now may be used in all stack commands such as stack build, and not only in stack setup

    The --setup-info-yaml may specify multiple locations for stack-setup.yaml files.

    πŸ‘‰ The stack upload can read first reads environment Variable $HACKAGE_USERNAME and $HACKAGE_PASSWORD if they are missing only then asks for username or password

    🚚 Fully remove GHCJS support.

    βœ‚ Remove the freeze command. It has been replaced by lock files.

    Behavior changes:

    βœ‚ Remove the deprecated --stack-setup-yaml command line argument in favor of --setup-info-yaml
    #2647

    πŸ”’ We now recommend checking in generated cabal files for repos. When generating lock files for
    πŸ“¦ extra-deps that only include package.yaml files, a deprecation warning will be generated.
    πŸ”’ Also, those packages will no longer be included in the generated lock files.
    πŸ‘€ See #5210.

    Other enhancements:

    βž• Add build-output-timestamps flag in yaml. Setting it to true
    πŸ— prefixes each build log output line with a timestamp.

    🏁 Show warning about local-programs-path with spaces on windows
    πŸ‘€ when running scripts. See
    #5013

    βž• Add ls dependencies json which will print dependencies as JSON.
    πŸ‘€ ls dependencies --tree is now ls dependencies tree. See
    #4424

    βœ‚ Remove warning for using Stack with GHC 8.8-8.10, and Cabal 3.0-3.2.

    πŸ‘ Allow relative paths in --setup-info-yaml and tool paths
    #3394

    βž• Added the --only-locals flag. See
    #5272

    πŸ› Bug fixes:

    ⬆️ Upgrade pantry: module mapping insertions into the database are now atomic.
    Previously, if you SIGTERMed at the wrong time while running a script, you
    could end up with an inconsistent database state.

    --resolver global doesn't retrieve snapshots list from the internet
    πŸ‘€ beause doesn't need it. See #5103

    πŸ›  Fix using relative links in haddocks output. See
    #4971.

    πŸ”’ Do not include generated cabal file information in lock files. See
    #5045.

    πŸ‘€ Use proper Hoogle executable path when installed automatically. See
    #4905

    πŸ›  Fix GHC version for batched package unregistration. See
    #4951

    πŸ‘€ Use Hoogle from the snapshot used and not the latest version. See
    #4905

    πŸ‘€ Resolve "'stty' is not recognized". See
    #4901

    πŸ›  Fix missing reconfigure check causing errors when a package gets
    πŸ‘€ used in multiple projects. See
    #5147

    πŸš€ Thanks to all our contributors for this release:

    • Adam McCullough
    • Akshay Mankar
    • Brian Wignall
    • Cheah Jer Fei
    • Chris Done
    • David Baynard
    • davit nalchevanidze
    • Dino Morelli
    • Emanuel Borsboom
    • Felix Yan
    • flip111
    • Flowers Safety
    • Fred Miller
    • Fyrbll
    • gdziadkiewicz
    • Good boy
    • Hypnoes.Liu
    • Iisus
    • Iustin Pop
    • ivanbakel
    • Javier Neira
    • Jeff Happily
    • jeffhappily
    • jneira
    • Justin Le
    • Kirill Zaborsky
    • Leif Metcalf
    • Leonhard Markert
    • Lokesh Mohanty
    • Matt Audesse
    • Michael Snoyman
    • Mihai Maruseac
    • NightRa
    • Phil Ruffwind
    • qinzhenlong
    • Robert Hensing
    • Sasha Bogicevic
    • Sibi
    • Sibi Prabakaran
    • Simon Michael
    • Steve Mao
    • Vlad Ki
    • Xia Li-yao

  • v2.3.x Changes

    πŸ”„ Changes since v2.1.3.1

    πŸš€ Release notes:

    Major changes:

    • πŸ”§ setup-info-locations yaml configuration now allows overwriting the default locations of stack-setup-2.yaml. #5031 #2983 #2913

    • πŸ”§ The setup-info configuration key now allows overwriting parts of the default setup-info

    • πŸ— The --setup-info-yaml command line flag now may be used in all stack commands such as stack build, and not only in stack setup

    • The --setup-info-yaml may specify multiple locations for stack-setup.yaml files.

    • πŸ‘‰ The stack upload can read first reads environment Variable $HACKAGE_USERNAME and $HACKAGE_PASSWORD if they are missing only then asks for username or password

    • 🚚 Fully remove GHCJS support.

    • βœ‚ Remove the freeze command. It has been replaced by lock files.

    Behavior changes:

    • βœ‚ Remove the deprecated --stack-setup-yaml command line argument in favor of --setup-info-yaml #2647

    • πŸ”’ We now recommend checking in generated cabal files for repos. When generating lock files for extra-deps that only include package.yaml files, a deprecation warning will be generated. Also, those packages will no longer be included in the generated lock files. See #5210.

    Other enhancements:

    • βž• Add build-output-timestamps flag in yaml. Setting it to true prefixes each build log output line with a timestamp.

    • 🏁 Show warning about local-programs-path with spaces on windows when running scripts. See #5013

    • βž• Add ls dependencies json which will print dependencies as JSON. ls dependencies --tree is now ls dependencies tree. See #4424

    • βœ‚ Remove warning for using Stack with GHC 8.8 and Cabal 3.0.

    • πŸ‘ Allow relative paths in --setup-info-yaml and tool paths #3394

    πŸ› Bug fixes:

    • ⬆️ Upgrade pantry: module mapping insertions into the database are now atomic. Previously, if you SIGTERMed at the wrong time while running a script, you could end up with an inconsistent database state.

    • --resolver global doesn't retrieve snapshots list from the internet beause doesn't need it. See #5103

    • πŸ›  Fix using relative links in haddocks output. See #4971.

    • πŸ”’ Do not include generated cabal file information in lock files. See #5045.

    • πŸ‘€ Use proper Hoogle executable path when installed automatically. See #4905

    • πŸ›  Fix GHC version for batched package unregistration. See #4951

    • πŸ‘€ Use Hoogle from the snapshot used and not the latest version. See #4905

    • πŸ‘€ Resolve "'stty' is not recognized". See #4901

    • πŸ›  Fix missing reconfigure check causing errors when a package gets used in multiple projects. See #5147

  • v2.3.0.1 Changes

    March 31, 2020

    πŸš€ First release candidate for v2.3

    πŸ”„ Changes since v2.1.3

    πŸš€ Release notes:

    Major changes:

    πŸ”§ setup-info-locations yaml configuration now allows overwriting the default locations of stack-setup-2.yaml.
    #5031
    #2983
    #2913

    πŸ”§ The setup-info configuration key now allows overwriting parts of the default setup-info

    πŸ— The --setup-info-yaml command line flag now may be used in all stack commands such as stack build, and not only in stack setup

    The --setup-info-yaml may specify multiple locations for stack-setup.yaml files.

    πŸ‘‰ The stack upload can read first reads environment Variable $HACKAGE_USERNAME and $HACKAGE_PASSWORD if they are missing only then asks for username or password

    🚚 Fully remove GHCJS support.

    βœ‚ Remove the freeze command. It has been replaced by lock files.

    Behavior changes:

    βœ‚ Remove the deprecated --stack-setup-yaml command line argument in favor of --setup-info-yaml
    #2647

    πŸ”’ We now recommend checking in generated cabal files for repos. When generating lock files for
    πŸ“¦ extra-deps that only include package.yaml files, a deprecation warning will be generated.
    πŸ”’ Also, those packages will no longer be included in the generated lock files.
    πŸ‘€ See #5210.

    Other enhancements:

    βž• Add build-output-timestamps flag in yaml. Setting it to true
    πŸ— prefixes each build log output line with a timestamp.

    🏁 Show warning about local-programs-path with spaces on windows
    πŸ‘€ when running scripts. See
    #5013

    βž• Add ls dependencies json which will print dependencies as JSON.
    πŸ‘€ ls dependencies --tree is now ls dependencies tree. See
    #4424

    βœ‚ Remove warning for using Stack with GHC 8.8 and Cabal 3.0.

    πŸ‘ Allow relative paths in --setup-info-yaml and tool paths
    #3394

    πŸ› Bug fixes:

    ⬆️ Upgrade pantry: module mapping insertions into the database are now atomic.
    Previously, if you SIGTERMed at the wrong time while running a script, you
    could end up with an inconsistent database state.

    --resolver global doesn't retrieve snapshots list from the internet
    πŸ‘€ beause doesn't need it. See #5103

    πŸ›  Fix using relative links in haddocks output. See
    #4971.

    πŸ”’ Do not include generated cabal file information in lock files. See
    #5045.

    πŸ‘€ Use proper Hoogle executable path when installed automatically. See
    #4905

    πŸ›  Fix GHC version for batched package unregistration. See
    #4951

    πŸ‘€ Use Hoogle from the snapshot used and not the latest version. See
    #4905

    πŸ‘€ Resolve "'stty' is not recognized". See
    #4901

    πŸ›  Fix missing reconfigure check causing errors when a package gets
    πŸ‘€ used in multiple projects. See
    #5147