v1.6.5

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

Bug fixes:

• 1.6.1 introduced a change that made some precompiled cache files use
  longer paths, sometimes causing builds to fail on windows. This has been
  fixed. See #3649
• Some unnecessary rebuilds when no files were changed are now avoided, by
  having a separate build cache for each component of a package. See
  #3732.
• Correct the behavior of promoting a package from snapshot to local
  package. This would get triggered when version bounds conflicted in
  a snapshot, which could be triggered via Hackage revisions for old
  packages. This also should allow custom snapshots to define
  conflicting versions of packages without issue. See
  Stackage issue #3185.
• When promoting packages from snapshot to local, we were
  occassionally discarding the actual package location content and
  instead defaulting to pulling the package from the index. We now
  correctly retain this information. Note that if you were affected by
  this bug, you will likely need to delete the binary build cache
  associated with the relevant custom snapshot. See
  #3714.
• --no-rerun-tests has been fixed. Previously, after running a test
  we were forgetting to record the result, which meant that all tests
  always ran even if they had already passed before. See
  #3770.
• Includes a patched version of hackage-security which fixes both
  some issues around asynchronous exception handling, and moves from
  directory locking to file locking, making the update mechanism
  resilient against SIGKILL and machine failure. See
  hackage-security #187
  and #3073.

Thanks to all our contributors for this release:

• Arnaud Spiwack
• Artyom
• Artyom Kazak
• Charles Reilly
• Dave Tapley
• Emanuel Borsboom
• Joshua Simmons
• Luke Murphy
• Michael Sloan
• Michael Snoyman
• Nicolas Mattia
• Paolo G. Giarrusso
• Samuel Lelièvre
• Simon Hengel
• Thomas Broadley
• tswelsh

v1.6.3

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

Enhancements:

• In addition to supporting .tar.gz and .zip files as remote archives,
  plain .tar files are now accepted too. This will additionally help with
  cases where HTTP servers mistakenly set the transfer encoding to gzip. See
  #3647.
• Links to docs.haskellstack.org ignore Stack version patchlevel.
• Downloading Docker-compatible stack binary ignores Stack version patchlevel.

Bug fixes:

• For versions of Cabal before 1.24, ensure that the dependencies of
  non-buildable components are part of the build plan to work around an old
  Cabal bug. See #3631.
• Run the Cabal file checking in the sdist command more reliably by
  allowing the Cabal library to flatten the
  GenericPackageDescription itself.

v1.6.1

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

Note: we are releasing a bit earlier than planned due to #3624. As such, not all the binaries have been built yet, but the commonly used 64-bit binaries of Linux static, macOS, and Windows are available.

In addition, the Windows installer and binary has not been codesigned (we are awaiting validation of a new codesign certificate), and you may see a "Windows Defender SmartScreen prevented an unrecognized app from starting" warning when you try to run them. If so, click on More info, and then click on the Run anyway button that appears.

Changes since v1.5.1

Major changes:

• Complete overhaul of how snapshots are defined, the packages and
  extra-deps fields, and a number of related items. For full
  details, please see
  the writeup on these changes. PR #3249,
  see the PR description for a number of related issues.
• Upgraded to version 2.0 of the Cabal library.

Behavior changes:

• The --install-ghc flag is now on by default. For example, if you
  run stack build in a directory requiring a GHC that you do not
  currently have, Stack will automatically download and install that
  GHC. You can explicitly set install-ghc: false or pass the flag
  --no-install-ghc to regain the previous behavior.
• stack ghci no longer loads modules grouped by package. This is
  always an improvement for plain ghci - it makes loading faster and
  less noisy. For intero, this has the side-effect that it will no
  longer load multiple packages that depend on TH loading relative
  paths. TH relative paths will still work when loading a single
  package into intero. See
  #3309
• Setting GHC options for a package via ghc-options: in your
  stack.yaml will promote it to a local package, providing for more
  consistency with flags and better reproducibility. See:
  #849
• The package-indices setting with Hackage no longer works with the
  00-index.tar.gz tarball, but must use the 01-index.tar.gz file
  to allow revised packages to be found.
• Options passsed via --ghci-options are now passed to the end of the
  invocation of ghci, instead of the middle. This allows using +RTS
  without an accompanying -RTS.
• When auto-detecting --ghc-build, tinfo6 is now preferred over
  standard if both versions of libtinfo are installed
• Addition of stack build --copy-compiler-tool, to allow tools like
  intero to be installed globally for a particular compiler.
  #2643
• Stack will ask before saving hackage credentials to file. This new
  prompt can be avoided by using the save-hackage-creds setting. Please
  see #2159.
• The GHCRTS environment variable will no longer be passed through to
  every program stack runs. Instead, it will only be passed through
  commands like exec, runghc, script, ghci, etc.
  See #3444.
• ghc-options: for specific packages will now come after the options
  specified for all packages / particular sets of packages. See
  #3573.
• The pvp-bounds feature is no longer fully functional, due to some
  issues with the Cabal library's printer. See
  #3550.

Other enhancements:

• The with-hpack configuration option specifies an Hpack executable to use
  instead of the Hpack bundled with Stack. Please
  see #3179.
• It's now possible to skip tests and benchmarks using --skip
  flag
• GitSHA1 is now StaticSHA256 and is implemented using the StaticSize 64 ByteString for improved performance.
  See #3006
• Dependencies via HTTP(S) archives have been generalized to allow
  local file path archives, as well as to support setting a
  cryptographic hash (SHA256) of the contents for better
  reproducibility.
• Allow specifying --git-branch when upgrading
• When running stack upgrade from a file which is different from the
  default executable path (e.g., on POSIX systems,
  ~/.local/bin/stack), it will now additionally copy the new
  executable over the currently running stack executable. If
  permission is denied (such as in /usr/local/bin/stack), the user
  will be prompted to try again using sudo. This is intended to
  assist with the user experience when the PATH environment variable
  has not been properly configured, see
  #3232.
• stack setup for ghcjs will now install alex and happy if
  they are not present. See
  #3109.
• Added stack ghci --only-main flag, to skip loading / importing
  all but main modules. See the ghci documentation page
  for further info.
• Allow GHC's colored output to show through. GHC colors output
  starting with version 8.2.1, for older GHC this does nothing.
  Sometimes GHC's heuristics would work fine even before this change,
  for example in stack ghci, but this override's GHC's heuristics
  when they're broken by our collecting and processing GHC's output.
• Extended the ghc-options field to support $locals, $targets,
  and $everything. See:
  #3329
• Better error message for case that stack ghci file targets are
  combined with invalid package targets. See:
  #3342
• For profiling now uses -fprof-auto -fprof-cafs instead of
  the deprecated -auto-all -caf-all. See:
  #3360
• Better descriptions are now available for stack upgrade --help. See:
  #3070
• When using Nix, nix-shell now depends always on gcc to prevent build errors
  when using the FFI. As ghc depends on gcc anyway, this doesn't increase the
  dependency footprint.
• --cwd DIR can now be passed to stack exec in order to execute the
  program in a different directory. See:
  #3264
• Plan construction will detect if you add an executable-only package
  as a library dependency, resulting in much clearer error
  messages. See:
  #2195.
• Addition of --ghc-options to stack script to pass options directly
  to GHC. See:
  #3454
• Add hpack package.yaml to build Stack itself
• Add ignore-revision-mismatch setting. See:
  #3520.
• Log when each individual test suite finishes. See:
  #3552.
• Avoid spurious rebuilds when using --file-watch by not watching files for
  executable, test and benchmark components that aren't a target. See:
  #3483.
• Stack will now try to detect the width of the running terminal
  (only on POSIX for the moment) and use that to better display
  output messages. Work is ongoing, so some messages will not
  be optimal yet. The terminal width can be overriden with the
  new --terminal-width command-line option (this works even on
  non-POSIX).
• Passing non local packages as targets to stack ghci will now
  cause them to be used as -package args along with package
  hiding.
• Detect when user changed .cabal file instead of package.yaml. This
  was implemented upstream in hpack. See
  #3383.
• Automatically run autoreconf -i as necessary when a configure
  script is missing. See
  #3534
• GHC bindists can now be identified by their SHA256 checksum in addition to
  their SHA1 checksum, allowing for more security in download.
• For filesystem setup-info paths, it's no longer assumed that the
  directory is writable, instead a temp dir is used. See
  #3188.

Bug fixes:

• stack hoogle correctly generates Hoogle databases. See:
  #3362
• stack --docker-help is now clearer about --docker implying
  system-ghc: true, rather than both --docker and --no-docker.
• stack haddock now includes package names for all modules in the
  Haddock index page. See:
  #2886
• Fixed an issue where Stack wouldn't detect missing Docker images
  properly with newer Docker versions.
  #3171
• Previously, cabal files with just test-suite could cause build to fail
  (#2862)
• If an invalid snapshot file has been detected (usually due to
  mismatched hashes), Stack will delete the downloaded file and
  recommend either retrying or filing an issue upstream. See
  #3319.
• Modified the flag parser within Stack to match the behavior of
  Cabal's flag parser, which allows multiple sequential dashes. See
  [#3345](https://gi...

v1.6.0.20171202

This is the first release candidate for v1.6.1.

Changes since the last v1.6 pre-release (v1.6.0.20171022):

Behavior changes:

• The package-indices setting with Hackage no longer works with the
  00-index.tar.gz tarball, but must use the 01-index.tar.gz file
  to allow revised packages to be found.
• The GHCRTS environment variable will no longer be passed through to
  every program stack runs. Instead, it will only be passed through
  commands like exec, runghc, script, ghci, etc.
  See #3444.
• ghc-options: for specific packages will now come after the options
  specified for all packages / particular sets of packages. See
  #3573.
• The pvp-bounds feature is no longer fully functional, due to some
  issues with the Cabal library's printer. See
  #3550.

Other enhancements:

• Plan construction will detect if you add an executable-only package
  as a library dependency, resulting in much clearer error
  messages. See:
  #2195.
• Addition of --ghc-options to stack script to pass options directly
  to GHC. See:
  #3454
• Add hpack package.yaml to build Stack itself
• Add ignore-revision-mismatch setting. See:
  #3520.
• Log when each individual test suite finishes. See:
  #3552.
• Avoid spurious rebuilds when using --file-watch by not watching files for
  executable, test and benchmark components that aren't a target. See:
  #3483.
• Stack will now try to detect the width of the running terminal
  (only on POSIX for the moment) and use that to better display
  output messages. Work is ongoing, so some messages will not
  be optimal yet. The terminal width can be overriden with the
  new --terminal-width command-line option (this works even on
  non-POSIX).
• Passing non local packages as targets to stack ghci will now
  cause them to be used as -package args along with package
  hiding.
• Detect when user changed .cabal file instead of package.yaml. This
  was implemented upstream in hpack. See
  #3383.
• Automatically run autoreconf -i as necessary when a configure
  script is missing. See
  #3534
• GHC bindists can now be identified by their SHA256 checksum in addition to
  their SHA1 checksum, allowing for more security in download.
• For filesystem setup-info paths, it's no longer assumed that the
  directory is writable, instead a temp dir is used. See
  #3188.

Bug fixes:

• When --pvp-bounds is enabled for sdist or upload, internal
  dependencies could cause errors when uploaded to hackage. This is
  fixed, see #3290
• Fixes a bug where nonexistent hackage versions would cause stack to
  suggest the same package name, without giving version info. See
  #3562
• Fixes a bug that has existed since 1.5.0, where
  stack setup --upgrade-cabal would say that Cabal is already the latest
  version, when it wasn't.
• Ensure that an extra-dep from a local directory is not treated as
  a $locals for GHC options purposes. See
  #3574.
• Building all executables only happens once instead of every
  time. See
  #3229 for
  more info.

v1.6.0.20171022

This is a pre-release for testing

Changes since v1.5.1

Major changes:

• Complete overhaul of how snapshots are defined, the packages and
  extra-deps fields, and a number of related items. For full
  details, please see
  the writeup on these changes. PR #3249,
  see the PR description for a number of related issues.
• Upgraded to version 2.0 of the Cabal library.

Behavior changes:

• The --install-ghc flag is now on by default. For example, if you
  run stack build in a directory requiring a GHC that you do not
  currently have, Stack will automatically download and install that
  GHC. You can explicitly set install-ghc: false or pass the flag
  --no-install-ghc to regain the previous behavior.
• stack ghci no longer loads modules grouped by package. This is
  always an improvement for plain ghci - it makes loading faster and
  less noisy. For intero, this has the side-effect that it will no
  longer load multiple packages that depend on TH loading relative
  paths. TH relative paths will still work when loading a single
  package into intero. See
  #3309
• Setting GHC options for a package via ghc-options: in your
  stack.yaml will promote it to a local package, providing for more
  consistency with flags and better reproducibility. See:
  #849
• Options passsed via --ghci-options are now passed to the end of the
  invocation of ghci, instead of the middle. This allows using +RTS
  without an accompanying -RTS.
• When auto-detecting --ghc-build, tinfo6 is now preferred over
  standard if both versions of libtinfo are installed
• Addition of stack build --copy-compiler-tool, to allow tools like
  intero to be installed globally for a particular compiler.
  #2643
• Stack will now try to detect the width of the running terminal
  (only on POSIX for the moment) and use that to better display
  output messages. Work is ongoing, so some messages will not
  be optimal yet. The terminal width can be overriden with the
  new --terminal-width command-line option (this works even on
  non-POSIX).
• Stack will ask before saving hackage credentials to file. This new
  prompt can be avoided by using the save-hackage-creds setting. Please
  see #2159.

Other enhancements:

• The with-hpack configuration option specifies an Hpack executable to use
  instead of the Hpack bundled with Stack. Please
  see #3179.
• It's now possible to skip tests and benchmarks using --skip
  flag
• GitSHA1 is now StaticSHA256 and is implemented using the StaticSize 64 ByteString for improved performance.
  See #3006
• Dependencies via HTTP(S) archives have been generalized to allow
  local file path archives, as well as to support setting a
  cryptographic hash (SHA256) of the contents for better
  reproducibility.
• Allow specifying --git-branch when upgrading
• When running stack upgrade from a file which is different from the
  default executable path (e.g., on POSIX systems,
  ~/.local/bin/stack), it will now additionally copy the new
  executable over the currently running stack executable. If
  permission is denied (such as in /usr/local/bin/stack), the user
  will be prompted to try again using sudo. This is intended to
  assist with the user experience when the PATH environment variable
  has not been properly configured, see
  #3232.
• stack setup for ghcjs will now install alex and happy if
  they are not present. See
  #3109.
• --ghc-options and --ghcjs-boot-options now parse their input, so
  multiple arguments can be passed in one option.
  See #3315
• Added stack ghci --only-main flag, to skip loading / importing
  all but main modules. See the ghci documentation page
  for further info.
• Allow GHC's colored output to show through. GHC colors output
  starting with version 8.2.1, for older GHC this does nothing.
  Sometimes GHC's heuristics would work fine even before this change,
  for example in stack ghci, but this override's GHC's heuristics
  when they're broken by our collecting and processing GHC's output.
• Extended the ghc-options field to support $locals, $targets,
  and $everything. See:
  #3329
• Better error message for case that stack ghci file targets are
  combined with invalid package targets. See:
  #3342
• For profiling now uses -fprof-auto -fprof-cafs instead of
  the deprecated -auto-all -caf-all. See:
  #3360
• Better descriptions are now available for stack upgrade --help. See:
  #3070
• When using Nix, nix-shell now depends always on gcc to prevent build errors
  when using the FFI. As ghc depends on gcc anyway, this doesn't increase the
  dependency footprint.
• --cwd DIR can now be passed to stack exec in order to execute the
  program in a different directory. See:
  #3264

Bug fixes:

• stack hoogle correctly generates Hoogle databases. See:
  #3362
• stack --docker-help is now clearer about --docker implying
  system-ghc: true, rather than both --docker and --no-docker.
• stack haddock now includes package names for all modules in the
  Haddock index page. See:
  #2886
• Fixed an issue where Stack wouldn't detect missing Docker images
  properly with newer Docker versions.
  #3171
• Previously, cabal files with just test-suite could cause build to fail
  (#2862)
• If an invalid snapshot file has been detected (usually due to
  mismatched hashes), Stack will delete the downloaded file and
  recommend either retrying or filing an issue upstream. See
  #3319.
• Modified the flag parser within Stack to match the behavior of
  Cabal's flag parser, which allows multiple sequential dashes. See
  #3345
• Now clears the hackage index cache if it is older than the
  downloaded index. Fixes potential issue if stack was interrupted when
  updating index.
  See #3033
• The Stack install script now respects the -d option.
  See #3366.
• stack script can now handle relative paths to source files.
  See #3372.
• Fixes explanation of why a target is needed by the build plan, when the
  target is an extra dependency from the commandline.
  See #3378.
• Previously, if you delete a yaml file from ~/.stack/build-plan, it would
  trust the etag and not re-download. Fixed in this version.
• Invoking stack --docker in parallel now correctly locks the sqlite database.
  See #3400.
• docs.haskellstack.org RTD documentation search is replaced by the mkdocs
  search. Please see
  #3376.
• stack clean now works with nix. See
  #3468.
• stack build --only-dependencies no longer builds local project packages
  that are depended on. See
  #3476.
• Properly handle relative paths stored in the precompiled cache files. See
  #3431.
• In some cases, Cabal does not realize that it needs to reconfigure, and must
  be told to do so automatically. This would manifest as a "shadowed
  dependency" error message. We now force a reconfigure whenever a dependency is
  built, even if the package ID remained the same. See
  #2781.

v1.5.1

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

Bug fixes:

• Stack eagerly tries to parse all cabal files related to a
  snapshot. Starting with Stackage Nightly 2017-07-31, snapshots are
  using GHC 8.2.1, and the ghc.cabal file implicitly referenced uses
  the (not yet supported) Cabal 2.0 file format. Future releases of
  Stack will both be less eager about cabal file parsing and support
  Cabal 2.0. This patch simply bypasses the error for invalid parsing.

v1.5.0

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

Behavior changes:

• stack profile and stack trace now add their extra RTS arguments for
  benchmarks and tests to the beginning of the args, instead of the end.
  See #2399
• Support for Git-based indices has been removed.

Other enhancements:

• stack setup allow to control options passed to ghcjs-boot with
  --ghcjs-boot-options (one word at a time) and --[no-]ghcjs-boot-clean
• stack setup now accepts a --install-cabal VERSION option which
  will install a specific version of the Cabal library globally.
• Updates to store-0.4.1, which has improved performance and better error
  reporting for version tags. A side-effect of this is that all of
  stack's binary caches will be invalidated.
• stack solver will now warn about unexpected cabal-install versions.
  See #3044
• Upstream packages unpacked to a temp dir are now deleted as soon as
  possible to avoid running out of space in /tmp.
  See #3018
• Add short synonyms for test-arguments and benchmark-arguments options.
• Adds STACK_WORK environment variable, to specify work dir.
  See #3063
• Can now use relative paths for extra-include-dirs and extra-lib-dirs.
  See #2830
• Improved bash completion for many options, including --ghc-options,
  --flag, targets, and project executables for exec.
• --haddock-arguments is actually used now when haddock is invoked
  during documentation generation.
• --[no-]haddock-hyperlink-source flag added which allows toggling
  of sources being included in Haddock output.
  See #3099
• stack ghci will now skip building all local targets, even if they have
  downstream deps, as long as it's registered in the DB.
• The pvp-bounds feature now supports adding -revision to the end of
  each value, e.g. pvp-bounds: both-revision. This means that, when
  uploading to Hackage, Stack will first upload your tarball with an
  unmodified .cabal file, and then upload a cabal file revision with
  the PVP bounds added. This can be useful—especially combined
  with the
  Stackage no-revisions feature—as
  a method to ensure PVP compliance without having to proactively fix
  bounds issues for Stackage maintenance.
• Expose a save-hackage-creds configuration option
• On GHC <= 7.8, filters out spurious linker warnings on windows
  See #3127
• Better error messages when creating or building packages which alias
  wired-in packages. See
  #3172.
• MinGW bin folder now is searched for dynamic libraries. See #3126
• When using Nix, nix-shell now depends always on git to prevent runtime errors
  while fetching metadata
• The stack unpack command now accepts a form where an explicit
  Hackage revision hash is specified, e.g. stack unpack foo-1.2.3@gitsha1:deadbeef. Note that this should be considered
  experimental, Stack will likely move towards a different hash
  format in the future.
• Binary "stack upgrade" will now warn if the installed executable is not
  on the PATH or shadowed by another entry.
• Allow running tests on tarball created by sdist and upload
  #717.

Bug fixes:

• Fixes case where stack build --profile might not cause executables /
  tests / benchmarks to be rebuilt.
  See #2984
• stack ghci file.hs now loads the file even if it isn't part of
  your project.
• stack clean --full now works when docker is enabled.
  See #2010
• Fixes an issue where cyclic deps can cause benchmarks or tests to be run
  before they are built.
  See #2153
• Fixes stack build --file-watch in cases where a directory is removed
  See #1838
• Fixes stack dot and stack list-dependencies to use info from the
  package database for wired-in-packages (ghc, base, etc).
  See #3084
• Fixes stack --docker build when user is part of libvirt/libvirtd
  groups on Ubuntu Yakkety (16.10).
  See #3092
• Switching a package between extra-dep and local package now forces
  rebuild (previously it wouldn't if versions were the same).
  See #2147
• stack upload no longer reveals your password when you type it on
  MinTTY-based Windows shells, such as Cygwin and MSYS2.
  See #3142
• stack script's import parser will now properly parse files that
  have Windows-style line endings (CRLF)

Thanks to all our contributors for this release:

• Aayush Kapoor
• Albert Netymk
• Alexey Kuleshevich
• Anders Kaseorg
• Arash Rouhani
• Bryan Richter
• Dawei LIU
• Dmitry Nikulin
• Domen Kožar
• Emanuel Borsboom
• Felix Yan
• Ivan Lazar Miljenovic
• James Hamilton
• Luke Murphy
• Marcin Tolysz
• Martin Kolinek
• Mateusz Kowalczyk
• Michael Sloan
• Michael Snoyman
• Niklas Hambüchen
• Noah Doersing
• Omari Norman
• Paolo G. Giarrusso
• Peter Stuart
• Ryan Scott
• Sergey Vinokurov
• Sibi Prabakaran
• Tej Chajed
• Tim Dysinger
• Tomáš Janoušek
• Vassil Keremidchiev

v1.4.0

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

Release notes:

• Docker images:
  fpco/stack-full and
  fpco/stack-run
  are no longer being built for LTS 8.0 and above.
  fpco/stack-build
  images continue to be built with a
  simplified process.
  #624

Major changes:

• A new command, script, has been added, intended to make the script
  interpreter workflow more reliable, easier to use, and more
  efficient. This command forces the user to provide a --resolver
  value, ignores all config files for more reproducible results, and
  optimizes the existing package check to make the common case of all
  packages already being present much faster. This mode does require
  that all packages be present in a snapshot, however.
  #2805

Behavior changes:

• The default package metadata backend has been changed from Git to
  the 01-index.tar.gz file, from the hackage-security project. This is
  intended to address some download speed issues from Github for
  people in certain geographic regions. There is now full support for
  checking out specific cabal file revisions from downloaded tarballs
  as well. If you manually specify a package index with only a Git
  URL, Git will still be used. See
  #2780

• When you provide the --resolver argument to the stack unpack
  command, any packages passed in by name only will be looked up in
  the given snapshot instead of taking the latest version. For
  example, stack --resolver lts-7.14 unpack mtl will get version
  2.2.1 of mtl, regardless of the latest version available in the
  package indices. This will also force the same cabal file revision
  to be used as is specified in the snapshot.

  Unpacking via a package identifier (e.g. stack --resolver lts-7.14 unpack mtl-2.2.1) will ignore any settings in the snapshot and take
  the most recent revision.

  For backwards compatibility with tools relying on the presence of a
  00-index.tar, Stack will copy the 01-index.tar file to
  00-index.tar. Note, however, that these files are different; most
  importantly, 00-index contains only the newest revisions of cabal
  files, while 01-index contains all versions. You may still need to
  update your tooling.

• Passing --(no-)nix-* options now no longer implies --nix, except for
  --nix-pure, so that the user preference whether or not to use Nix is
  honored even in the presence of options that change the Nix behavior.

Other enhancements:

• Internal cleanup: configuration types are now based much more on lenses
• stack build and related commands now allow the user to disable debug symbol stripping
  with new --no-strip, --no-library-stripping, and --no-executable-shipping flags,
  closing #877.
  Also turned error message for missing targets more readable (#2384)
• stack haddock now shows index.html paths when documentation is already up to
  date. Resolved #781
• Respects the custom-setup field introduced in Cabal 1.24. This
  supercedes any explicit-setup-deps settings in your stack.yaml
  and trusts the package's .cabal file to explicitly state all its
  dependencies.
• If system package installation fails, get-stack.sh will fail as well. Also
  shows warning suggesting to run apt-get update or similar, depending on the
  OS.
  (#2898)
• When stack ghci is run with a config with no packages (e.g. global project),
  it will now look for source files in the current work dir.
  (#2878)
• Bump to hpack 0.17.0 to allow custom-setup and !include "..." in package.yaml.
• The script interpreter will now output error logging. In particular,
  this means it will output info about plan construction errors.
  (#2879)
• stack ghci now takes --flag and --ghc-options again (inadverently
  removed in 1.3.0).
  (#2986)
• stack exec now takes --rts-options which passes the given arguments inside of
  +RTS ... args .. -RTS to the executable. This works around stack itself consuming
  the RTS flags on Windows. (#2986)
• Upgraded http-client-tls version, which now offers support for the
  socks5:// and socks5h:// values in the http_proxy and https_proxy
  environment variables.

Bug fixes:

• Bump to hpack 0.16.0 to avoid character encoding issues when reading and
  writing on non-UTF8 systems.
• stack ghci will no longer ignore hsSourceDirs that contain ... (#2895)
• stack list-dependencies --license now works for wired-in-packages,
  like base. (#2871)
• stack setup now correctly indicates when it uses system ghc
  (#2963)
• Fix to stack config set, in 1.3.2 it always applied to
  the global project.
  (#2709)
• Previously, cabal files without exe or lib would fail on the "copy" step.
  (#2862)
• stack upgrade --git now works properly. Workaround for affected
  versions (>= 1.3.0) is to instead run stack upgrade --git --source-only.
  (#2977)
• Added support for GHC 8's slightly different warning format for
  dumping warnings from logs.
• Work around a bug in Cabal/GHC in which package IDs are not unique
  for different source code, leading to Stack not always rebuilding
  packages depending on local packages which have
  changed. (#2904)

Thanks to all our contributors for this release:

• Aditya Siram
• Alexey Zabelin
• Alexis Williams
• Andreas Klebinger
• Dale Wijnand
• Echo Nolan
• Emanuel Borsboom
• Franz Thoma
• Giovanni
• Ian Sullivan
• Jens Petersen
• Justus Adam
• Luke Murphy
• Marcin Tolysz
• Matt Gambogi
• Michael Sloan
• Michael Snoyman
• Michiel Derhaeg
• Piotr Bogdan
• Randall Britten
• Ryan Scott
• Shlomo Zaks
• Simon Jakobi
• spikefoo
• Steven Syrek
• tallen-imvu
• Thomas Allen
• Tom Feron
• Tomas Janousek
• Tommaso Piazza
• Vincent Hanquez
• YPares
• Yuriy Syrovetskiy
• Yves Parès (Ywen)

v1.3.2

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

This is a small bug fix release.

Bug fixes:

• stack config set can now be used without a compiler installed
  #2852.
• get-stack.sh now installs correct binary on ARM for generic linux and raspbian,
  closing #2856.
• Correct the testing of whether a package database exists by checking
  for the package.cache file itself instead of the containing
  directory.
• Revert a change in the previous release which made it impossible to
  set local extra-dep packages as targets. This was overkill; we
  really only wanted to disable their test suites, which was already
  handled by a later
  patch. #2849
• stack new always treats templates as being UTF-8 encoding,
  ignoring locale settings on a local machine. See
  Yesod mailing list discussion

Thanks to our contributors for this release:

• Alexander Kjeldaas
• Emanuel Borsboom
• Marcin Tolysz
• Michael Sloan
• Michael Snoyman

v1.3.0

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

Release notes:

• For the next stack release after this one, we are planning
  changes to our Linux releases, including dropping our Ubuntu,
  Debian, CentOS, and Fedora package repositories and switching to
  statically linked binaries. See
  #2534.
  Note that upgrading without a package manager has gotten easier
  with new binary upgrade support in stack upgrade (see the Major
  Changes section below for more information). In addition, the
  get.haskellstack.org script no longer installs from Ubuntu,
  Debian, CentOS, or Fedora package repositories. Instead it places
  a generic binary in /usr/local/bin.

Major changes:

• Stack will now always use its own GHC installation, even when a suitable GHC
  installation is available on the PATH. To get the old behaviour, use
  the --system-ghc flag or run stack config set system-ghc --global true.
  Docker- and Nix-enabled projects continue to use the GHC installations
  in their environment by default.

  NB: Scripts that previously used stack in combination with a system GHC
  installation should now include a stack setup line or use the --install-ghc
  flag.
  #2221

• stack ghci now defaults to skipping the build of target packages, because
  support has been added for invoking "initial build steps", which create
  autogen files and run preprocessors. The --no-build flag is now deprecated
  because it should no longer be necessary. See
  #1364

• Stack is now capable of doing binary upgrades instead of always
  recompiling a new version from source. Running stack upgrade will
  now default to downloading a binary version of Stack from the most
  recent release, if one is available. See stack upgrade --help for
  more options.
  #1238

Behavior changes:

• Passing --resolver X with a Stack command which forces creation of a global
  project config, will pass resolver X into the initial config.
  See #2579.
• Switch the "Run from outside project" messages to debug-level, to
  avoid spamming users in the normal case of non-project usage
• If a remote package is specified (such as a Git repo) without an explicit
  extra-dep setting, a warning is given to the user to provide one
  explicitly.

Other enhancements:

• stack haddock now supports --haddock-internal. See
  #2229
• Add support for system-ghc and install-ghc fields to stack config set command.
• Add ghc-build option to override autodetected GHC build to use (e.g. gmp4,
  tinfo6, nopie) on Linux.
• stack setup detects systems where gcc enables PIE by default (such as Ubuntu
  16.10 and Hardened Gentoo) and adjusts the GHC configure options accordingly.
  #2542
• Upload to Hackage with HTTP digest instead of HTTP basic.
• Make stack list-dependencies understand all of the stack dot options too.
• Add the ability for stack list-dependencies to list dependency licenses by
  passing the --license flag.
• Dump logs that contain warnings for any local non-dependency packages
  #2545
• Add the dump-logs config option and --dump-logs command line
  option to get full build output on the
  console. #426
• Add the --open option to "stack hpc report" command, causing the report to
  be opened in the browser.
• The stack config set command now accepts a --global flag for suitable fields
  which causes it to modify the global user configuration (~/.stack/config.yaml)
  instead of the project configuration.
  #2675
• Information on the latest available snapshots is now downloaded from S3 instead of
  stackage.org, increasing reliability in case of stackage.org outages.
  #2653
• stack dot and stack list-dependencies now take targets and flags.
  #1919
• Deprecate stack setup --stack-setup-yaml for --setup-info-yaml based
  on discussion in #2647.
• The --main-is flag for GHCI now implies the TARGET, fixing
  #1845.
• stack ghci no longer takes all build options, as many weren't useful
  #2199
• --no-time-in-log option, to make verbose logs more diffable
  #2727
• --color option added to override auto-detection of ANSI support
  #2725
• Missing extra-deps are now warned about, adding a degree of typo detection
  #1521
• No longer warns about missing build-tools if they are on the PATH.
  #2235
• Replace enclosed-exceptions with safe-exceptions.
  #2768
• The install location for GHC and other programs can now be configured with the
  local-programs-path option in config.yaml.
  #1644
• Added option to add nix dependencies as nix GC roots
• Proper pid 1 (init) process for stack exec with Docker
• Dump build logs if they contain warnings.
  #2545
• Docker: redirect stdout of docker pull to stderr so that
  it will not interfere with output of other commands.
• Nix & docker can be activated at the same time, in order to run stack in a nix-shell
  in a container, preferably from an image already containing the nix dependencies
  in its /nix/store
• Stack/nix: Dependencies can be added as nix GC roots, so they are not removed
  when running nix-collect-garbage

Bug fixes:

• Fixed a gnarly bug where programs and package tarballs sometimes have
  corrupted downloads. See
  #2657.
• Add proper support for non-ASCII characters in file paths for the sdist command.
  See #2549
• Never treat extra-dep local packages as targets. This ensures
  things like test suites are not run for these packages, and that
  build output is not hidden due to their presence.
• Fix a resource leak in sinkProcessStderrStdout which could affect
  much of the codebase, in particular copying precompiled
  packages. #1979
• Docker: ensure that interrupted extraction process does not cause corrupt file
  when downloading a Docker-compatible Stack executable
  #2568
• Fixed running stack hpc report on package targets.
  #2664
• Fix a long-standing performance regression where stack would parse the .dump-hi
  files of the library components of local packages twice.
  #2658
• Fixed a regression in "stack ghci --no-load", where it would prompt for a main
  module to load. #2603
• Build Setup.hs files with the threaded RTS, mirroring the behavior of
  cabal-install and enabling more complex build systems in those files.
• Fixed a bug in passing along --ghc-options to ghcjs. They were being
  provided as --ghc-options to Cabal, when it needs to be --ghcjs-options.
  #2714
• Launch Docker from the project root regardless of the working
  directory Stack is invoked from. This means paths relative to the project root
  (e.g. environment files) can be specified in stack.yaml's docker run-args.
• stack setup --reinstall now behaves as expected.
  #2554

Thanks to all our contributors for this release:

• Alexis Williams
• devlinzed
• Echo Nolan
• Emanuel Borsboom
• Eric Thomas
• Felix Yan
• Francesco Mazzoli
• Geoffrey Noel
• Gábor Lipták
• Harendra Kumar
• ickc
• Keshav Kini
• Luke Murphy
• Marcin Tolysz
• Michael Sloan
• Michael Snoyman
• mrkkrp
• osbugs
• Paolo G. Giarrusso
• Reuben D'Netto
• Robbin C
• Ruud van Asseldonk
• Sam Doshi
• Simon Jakobi
• Tomasz Lewowski
• U-CIQDEV
• bazerman
• whatsthepoint
• Yves Parès (Ywen)