Changelog History
Page 3
-
v1.9.0.1 Changes
September 23, 2018π First release candidate for v1.9
π Changes since v1.7.1
π Release notes:
- π§ Statically linked Linux bindists are back again, thanks to @nh2.
π§ Please try thestack-1.9.0.1-linux-x86_64-static.tar.gz
distribution if using Linux , since it will be the default installed version once v1.9.1 is released. - π We will be deleting the Ubuntu, Debian, CentOS, Fedora, and Arch package repos from
download.fpcomplete.com
soon. These have been deprecated for over a year and have not received new releases, but were left in place for compatibility with older scripts.
Major changes:
- β¬οΈ
GHCJS
support is being downgraded to 'experimental'. A warning notifying the user of the experimental status ofGHCJS
will be displayed.
Behavior changes:
ghc-options
fromstack.yaml
are now appended toghc-options
from
config.yaml
, whereas before they would be replaced.- π
stack build
will now announce when sublibraries of a package are being
π build, in the same way executables, tests, benchmarks and libraries are
announced stack sdist
will now announce the destination of the generated tarball,
regardless of whether or not it passed the sanity checks- β¬οΈ The
--upgrade-cabal
option tostack setup
has been
π deprecated. This feature no longer works with GHC 8.2 and
later. Furthermore, the reason for this flag originally being
implemented was drastically lessened once Stack started using the
π snapshot'sCabal
library for custom setups. See:
#4070. - With the new namespaced template feature,
stack templates
is no
longer able to meaningfully display a list of all templates
available. Instead, the command will download and display a
help file
π with more information on how to discover templates. See:
#4039 - π Build tools are now handled in a similar way to
cabal-install
. In
π particular, for legacybuild-tools
fields, we use a hard-coded
π list of build tools in place of looking up build tool packages in a
tool map. This both brings Stack's behavior closer into line with
cabal-install
, avoids some bugs, and opens up some possible
π optimizations/laziness. See:
#4125. - Mustache templating is not applied to large files (over 50kb) to
π avoid performance degredation. See:
#4133. - π¦
stack upload
signs the package by default, as documented.--no-signature
turns the signing off.
#3739 - In case there is a network connectivity issue while trying to
download a template, stack will check whether that template had
been downloaded before. In that case, the cached version will be
π used. See #3850.
Other enhancements:
- π On Windows before Windows 10, --color=never is the default on terminals that
π can support ANSI color codes in output only by emulation - π On Windows, recognise a 'mintty' (false) terminal as a terminal, by default
- π
stack build
issues a warning whenbase
is explicitly listed in
extra-deps
ofstack.yaml
- π
stack build
suggests trying another GHC version should the build
plan end up requiring unattainablebase
version. - π A new sub command
run
has been introduced to build and run a specified executable
similar tocabal run
. If no executable is provided as the first argument, it
0οΈβ£ defaults to the first available executable in the project. - π
stack build
missing dependency suggestions (on failure to construct a valid
π build plan because of missing deps) are now printed with their latest
π cabal file revision hash. See
#4068. - β Added new
--tar-dir
option tostack sdist
, that allows to copy
the resulting tarball to the specified directory. - π» Introduced the
--interleaved-output
command line option and
πbuild.interleaved-output
config value which causes multiple concurrent
π builds to dump to stderr at the same time with apackagename>
prefix. See
#3225. - 0οΈβ£ The default retry strategy has changed to exponential backoff.
This should help with
#3510. stack new
now allows template names of the formusername/foo
to
π download from a user other thancommercialstack
on Github, and can be prefixed
with the servicegithub:
,gitlab:
, orbitbucket:
. #4039- π Switch to
githash
to include some unmerged bugfixes ingitrev
Suggestion to add'allow-newer': true
now shows path to user config
file where this flag should be put into #3685 - π
stack ghci
now asks which main target to load before doing the build,
rather than after - β¬οΈ Bump to hpack 0.29.0
- With GHC 8.4 and later, Haddock is given the
--quickjump
flag. - π¦ It is possible to specify the Hackage base URL to upload packages to, instead
0οΈβ£ of the default ofhttps://hackage.haskell.org/
, by usinghackage-base-url
π§ configuration option. - When using Nix, if a specific minor version of GHC is not requested, the
β latest minor version in the given major branch will be used automatically.
π Bug fixes:
stack ghci
now does not invalidate.o
files on repeated runs,
meaning any modules compiled with-fobject-code
will be cached
π between ghci runs. See
#4038.~/.stack/config.yaml
andstack.yaml
terminating by newline- π The previous released caused a regression where some
stderr
from the
ghc-pkg
command showed up in the terminal. This output is now silenced. - π A regression in recompilation checking introduced in v1.7.1 has been fixed.
π See #4001 - π¦
stack ghci
on a package with internal libraries was erroneously looking
π¦ for a wrong package corresponding to the internal library and failing to
π load any module. This has been fixed now and changes to the code in the
π library and the sublibrary are properly tracked. See
#3926. - π For packages with internal libraries not depended upon,
stack build
used
π to fail the build process since the internal library was not built but it
π was tried to be registered. This is now fixed by always building internal
π libraries. See
#3996. --no-nix
was not respected under NixOS- π Fix a regression which might use a lot of RAM. See
#4027. - Order of commandline arguments does not matter anymore.
π See #3959 - When prompting users about saving their Hackage credentials on upload,
flush to stdout before waiting for the response so the prompt actually
π displays. Also fixes a similar issue with ghci target selection prompt. - If
cabal
is not on PATH, runningstack solver
now prompts the user
to runstack install cabal-install
- π
stack build
now succeeds in building packages which contain sublibraries
β which are dependencies of executables, tests or benchmarks but not of the
π main library. See
#3787. - β
Sublibraries are now properly considered for coverage reports when the test
suite depends on the internal library. Before, stack was erroring when
π trying to generate the coverage report, see
#4105. - Sublibraries are now added to the precompiled cache and recovered from there
β‘οΈ when the snapshot gets updated. Previously, updating the snapshot when there
π was a package with a sublibrary in the snapshot resulted in broken builds.
π This is now fixed, see
#4071. - π¨ [#4114] Stack pretty prints error messages with proper
error
logging
β level instead ofwarning
now. This also fixes self-executing scripts
not piping plan construction errors from runhaskell to terminal (issue
#3942). - π Fix invalid "While building Setup.hs" when Cabal calls fail. See:
#3934 - π¦
stack upload
signs the package by default, as documented.--no-signature
turns the signing off.
#3739
- π§ Statically linked Linux bindists are back again, thanks to @nh2.
-
v1.7.1 Changes
April 27, 2018β¬οΈ See https://haskellstack.org for installation and upgrade instructions.
π Changes since v1.6.5:
π Release notes:
- aarch64 (64-bit ARM) bindists are now available for the first time.
- π§ Statically linked Linux bindists are no longer available, due to difficulty with GHC 8.2.2 on Alpine Linux.
- π§ 32-bit Linux GMP4 bindists for CentOS 6 are no longer available, since GHC 8.2.2 is no longer being built for that platform.
Major changes:
- β¬οΈ Upgrade from Cabal 2.0 to Cabal 2.2
Behavior changes:
- π§
stack setup
no longer uses different GHC configure options on Linux
0οΈβ£ distributions that use GCC with PIE enabled by default. GHC detects
βͺ this itself since ghc-8.0.2, and Stack's attempted workaround for older
π versions caused more problems than it solved. stack new
no longer initializes a project if the project template contains
a stack.yaml file.
Other enhancements:
- A new sub command
ls
has been introduced to stack to view
local and remote snapshots present in the system. Usestack ls snapshots --help
to get more details about it. - π
list-dependencies
has been deprecated. The functionality has
π to accessed through the newls dependencies
interface. See
#3669
for details. - Specify User-Agent HTTP request header on every HTTP request.
π See #3628 for details. stack setup
looks for GHC bindists and installations by any OS key
that is compatible (rather than only checking a single one). This is
π§ relevant on Linux where different distributions may have different
combinations of libtinfo 5/6, ncurses 5/6, and gmp 4/5, and will allow
π simpifying the setup-info metadata YAML for future GHC releases.- π The build progress bar reports names of packages currently building.
- π§
stack setup --verbose
causes verbose output of GHC configure process.
π See #3716 - π Improve the error message when an
extra-dep
from a path or git reference can't be found
π See #3808 - π Nix integration is now disabled on windows even if explicitly enabled,
π since it isn't supported. See
#3600 - π
stack build
now supports a new flag--keep-tmp-files
to retain intermediate
files and directories for the purpose of debugging.
It is best used with ghc's equivalent flag,
π i.e.stack build --keep-tmp-files --ghc-options=-keep-tmp-files
.
π See #3857 - π Improved error messages for snapshot parse exceptions
- π
stack unpack
now supports a--to /target/directory
option to
π¦ specify where to unpack the package into - π
stack hoogle
now supports a new flag--server
that launches local
π Hoogle server on port 8080. See
#2310
π Bug fixes:
- The script interpreter's implicit file arguments are now passed before other
π arguments. See #3658.
In particular, this makes it possible to pass-- +RTS ... -RTS
to specify
RTS arguments used when running the script. - Don't ignore the template
year
parameter in config files, and clarify the
π surrounding documentation. See
#2275. - Benchmarks used to be run concurrently with other benchmarks
π and build steps. This is non-ideal because CPU usage of other processes
may interfere with benchmarks. It also prevented benchmark output from
π being displayed by default. This is now fixed. See
#3663. - π¦
stack ghci
now allows loading multiple packages with the same
π module name, as long as they have the same filepath. See
#3776. stack ghci
no longer always adds a dependency onbase
. It is
now only added when there are no local targets. This allows it to
π be to load code that uses replacements forbase
. See
#3589stack ghci
now uses correct paths for autogen files with
#3791- π¦ When a package contained sublibraries, stack was always recompiling the
π¦ package. This has been fixed now, no recompilation is being done because of
π sublibraries. See #3899. - The
get-stack.sh
install script now matches manual instructions
when it comes to Debian/Fedora/CentOS install dependencies. - Compile Cabal-simple with gmp when using Nix.
π See #2944 stack ghci
now replaces the stack process with ghci. This improves
π¦ signal handling behavior. In particular, handling of Ctrl-C. To make
this possible, the generated files are now left behind after exit.
The paths are based on hashing file contents, and it's stored in the
system temporary directory, so this shouldn't result in too much
π garbage. See
#3821.
π Thanks to all our contributors for this release:
- Alexey Kuleshevich
- Andrei Dziahel
- Andrew Cowie
- Daniel Bergey
- David Baynard
- Domen KoΕΎar
- Don Waldhalm
- Emanuel Borsboom
- Geoffrey Noel
- Ivan Kasatenko
- Jan von Loewenstein
- Joshua Simmons
- Kirill Elagin
- Krishnan Parthasarathi
- Luke Murphy
- Matt Spaulding
- Matthias Braun
- Maximilian Tagher
- Michael Sloan
- Michael Snoyman
- Mihai Maruseac
- Mike Pilgrem
- Mitchell Rosen
- Nicolas Mattia
- Niklas HambΓΌchen
- Oleg Grenrus
- Reuben D'Netto
- Robert J. Macomber
- Sibi Prabakaran
- silky
- Simon Hengel
- Tero LaxstrΓΆm
- tswelsh
- Yuji Yamamoto
-
v1.6.5 Changes
π Bug fixes:
- 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.
-
v1.6.3 Changes
β¨ 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 togzip
. 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 theGenericPackageDescription
itself.
- π In addition to supporting
-
v1.6.3.1 Changes
π Hackage-only release with no user facing changes (updated to build with π newer version of hpack dependency).
-
v1.6.1 Changes
Major changes:
- π¦ Complete overhaul of how snapshots are defined, the
packages
andextra-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:
- 0οΈβ£ The
--install-ghc
flag is now on by default. For example, if you runstack build
in a directory requiring a GHC that you do not currently have, Stack will automatically download and install that GHC. You can explicitly setinstall-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 yourstack.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 the00-index.tar.gz
tarball, but must use the01-index.tar.gz
file to allow revised packages to be found. - Options passed 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 overstandard
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 likeexec
,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 nowStaticSHA256
and is implemented using theStaticSize 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 runningstack
executable. If permission is denied (such as in/usr/local/bin/stack
), the user will be prompted to try again usingsudo
. This is intended to assist with the user experience when thePATH
environment variable has not been properly configured, see #3232. stack setup
for ghcjs will now installalex
andhappy
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 tostack 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
tostack 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 overridden 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 aconfigure
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
- 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.
- 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.
- π¦ Complete overhaul of how snapshots are defined, the
-
v1.6.1.1 Changes
π Hackage-only release with no user facing changes (updated to build with π newer dependency versions).
-
v1.5.1 Changes
π 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.
- π 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
-
v1.5.0 Changes
Behavior changes:
stack profile
andstack 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
andbenchmark-arguments
options. - β Adds
STACK_WORK
environment variable, to specify work dir. See #3063 - Can now use relative paths for
extra-include-dirs
andextra-lib-dirs
. See #2830 - π Improved bash completion for many options, including
--ghc-options
,--flag
, targets, and project executables forexec
. --haddock-arguments
is actually used now whenhaddock
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
andstack 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)
-
v1.4.0 Changes
π 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 thestack 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 ofmtl
, 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 the01-index.tar
file to00-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 anyexplicit-setup-deps
settings in yourstack.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 runapt-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 "..."
inpackage.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 (inadvertently 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. (#2640)- β¬οΈ Upgraded
http-client-tls
version, which now offers support for thesocks5://
andsocks5h://
values in thehttp_proxy
andhttps_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 runstack 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)