Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

haskell-stack 3.3.1 #202648

Merged
merged 2 commits into from
Dec 28, 2024
Merged

haskell-stack 3.3.1 #202648

merged 2 commits into from
Dec 28, 2024

Conversation

BrewTestBot
Copy link
Member

Created by brew bump


Created with brew bump-formula-pr.

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

Changes since v3.1.1:

Behavior changes:

  • Stack interprets consecutive line ends in the value of the user-message project-specific configuration option as a single blank line. Previously all line ends were interpreted as white space.
  • Stack no longer supports Docker versions before Docker 1.9.1 and, consequently, if a Docker container is not being run 'detached', its standard input channel will always be kept open. (Before Docker 1.9.1 the use of an interactive container could hang in certain circumstances.)
  • On Windows, Stack will always warn (message S-8432) if there is a space character in Stack's 'programs' path, as GHC 9.4.1 and later do not work if there is a space in the path to the ghc executable. S-8432 now presents as a warning and not an error.
  • Stack respects the --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:

  • Consider GHC 9.10 to be a tested compiler and remove warnings.
  • Consider Cabal 3.12 to be a tested library and remove warnings.
  • Add flags --run-tests and --run-benchmarks (the existing defaults) to Stack's build command, which take precedence over the existing no-run-tests and no-run-benchmarks configuration options, respectively.
  • In configuration files, the notify-if-no-run-tests and notify-if-no-run-benchmarks keys are introduced, to allow the exisitng notification to be muted if unwanted.

Bug fixes:

  • Stack's in-app messages refer to https://haskellstack.org as currently structured. (Most URLs in older Stack versions are redirected.)
  • Stack's upgrade command only treats the current running Stack executable as 'stack' if the executable file is named stack 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 and stack bench --no-run-benchmarks --dry-run no longer reports that Stack would benchmark project packages with benchmarks.
  • StackSetupShim compiles with Cabal >= 3.14.0.0.

Thanks to all our contributors for this release:

  • Andrew Nguyen
  • Luka Leer
  • Mike Pilgrem
  • Olivier Benz

@github-actions github-actions bot added haskell Haskell use is a significant feature of the PR or issue bump-formula-pr PR was created using `brew bump-formula-pr` labels Dec 28, 2024
Copy link
Contributor

🤖 An automated task has requested bottles to be published to this PR.

@github-actions github-actions bot added the CI-published-bottle-commits The commits for the built bottles have been pushed to the PR branch. label Dec 28, 2024
@BrewTestBot BrewTestBot added this pull request to the merge queue Dec 28, 2024
Merged via the queue into master with commit a9ad730 Dec 28, 2024
15 checks passed
@BrewTestBot BrewTestBot deleted the bump-haskell-stack-3.3.1 branch December 28, 2024 17:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bump-formula-pr PR was created using `brew bump-formula-pr` CI-published-bottle-commits The commits for the built bottles have been pushed to the PR branch. haskell Haskell use is a significant feature of the PR or issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants