See README for installation and upgrade instructions.
“stack setup” now supports building and booting GHCJS from source tarball.
On Windows, build directories no longer display “pretty” information (like x86_64-windows/Cabal-220.127.116.11), but rather a hash of that content. The reason is to avoid the 260 character path limitation on Windows. See #1027
Rename config files and clarify their purposes #969
~/.stack/stack.yaml → ~/.stack/config.yaml
~/.stack/global → ~/.stack/global-project
/etc/stack/config → /etc/stack/config.yaml
Old locations still supported, with deprecation warnings
New command “stack eval CODE”, which evaluates to “stack exec ghc — -e CODE”.
No longer install git on Windows #1046. You can still get this behavior by running the following yourself: stack exec -- pacman -Sy --noconfirm git.
Typing enter during —file-watch triggers a rebuild #1023
Use Haddock’s --hyperlinked-source (crosslinked source), if available #1070
Use Stack-installed GHCs for stack init --solver#1072
By default, stack no longer rebuilds a package due to GHC options changes. This behavior can be tweaked with the rebuild-ghc-options setting. #1089
By default, ghc-options are applied to all local packages, not just targets. This behavior can be tweaked with the apply-ghc-options setting. #1089
Docker: download or override location of stack executable to re-run in container #974
Docker: when Docker Engine is remote, don’t run containerized processes as host’s UID/GID #194
Docker: set-user option to enable/disable running containerized processes as host’s UID/GID #194
Custom Setup.hs files are now precompiled instead of interpreted. This should be a major performance win for certain edge cases (biggest example: building Cabal itself) while being either neutral or a minor slowdown for more common cases.
stack test --coverage now also generates a unified coverage report for multiple test-suites / packages. In the unified report, test-suites can contribute to the coverage of other packages.