Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Created by
brew bump
Created with
brew bump-formula-pr
.release notes
user-message
project-specific configuration option as a single blank line. Previously all line ends were interpreted as white space.ghc
executable. S-8432 now presents as a warning and not an error.--no-run-tests
and--no-run-benchmarks
flags when determining build actions. Previously Stack respected the flags when executing the run test suites or run benchmarks actions for each targeted project package.Other enhancements:
--run-tests
and--run-benchmarks
(the existing defaults) to Stack'sbuild
command, which take precedence over the existingno-run-tests
andno-run-benchmarks
configuration options, respectively.notify-if-no-run-tests
andnotify-if-no-run-benchmarks
keys are introduced, to allow the exisitng notification to be muted if unwanted.Bug fixes:
upgrade
command only treats the current running Stack executable as 'stack
' if the executable file is namedstack
or, on Windows,stack.exe
. Previously only how it was invoked was considered.stack test --no-run-tests --dry-run
no longer reports that Stack would test project packages with test suites andstack bench --no-run-benchmarks --dry-run
no longer reports that Stack would benchmark project packages with benchmarks.StackSetupShim
compiles withCabal >= 3.14.0.0
.Thanks to all our contributors for this release: