Hannes Siebenhandl authored 1 year ago and Mikolaj Konarski committed 1 year ago

The runner allows the tests to use extra dependencies and the custom Prelude
from 'cabal-testsuite'.
However, if the tests use a dependency, say 'directory', and there are two
packages with the same unit id available in the store, the test fails since
it doesn't know which one to pick.
By including an extra dependency to directory, we force the test runner to
use a specific version directory, fixing the test failure.

Require version 3,11 of Cabal to support --semaphore flag

Fixes #9197

Fix AutogenModulesToggling test

By converting this to a setupTest we use the in-tree Cabal library
rather than relying on a proxy of the GHC version to provide the right
Cabal library version.

Supersedes #9398

Note how to do "not equal" with constraints

Co-authored-by: Javier Sagredo <jasataco@gmail.com>
Co-authored-by: Andrea Bedini <andrea.bedini@tweag.io>
Co-authored-by: Andrea Bedini <andrea@andreabedini.com>

Add reinstall test to LinkerOptions/NonignoredConfigs

Move documentation about how to use backpack

Do not run CI for documentation changes

The github workflows are not run if the
changes are completely contained within
the doc/ subdirectory. The only exception
is the users-guide.yml github action.

Co-authored-by: Artem Pelenitsyn <a.pelenitsyn@gmail.com>

Add instance Ord for Field, FieldLine, SectionArg and Name

Restructure user guide into top-level guides, reference and explanation parts

The goal is for users to easier find pages for typical problems through search engines and page navigation.
- The top-level layout is based on the popular documentation structure by https://documentation.divio.com/ to give a
   clear structure to users and future documentation contributors:
  * Guides: Present a solution to a single, atomic, typical user problem.
  * Reference: Describe user API (CLI fields, syntax etc) with technical rigour and completeness.
  * Explanation: Discuss background information, scope, design decisions etc.
- Move existing documentation roughly into these categories with minimal editing as the basis for further editing.
- Rename guide titles to mention how-to for improving SEO.
- Rename some files to improve SEO since that name becomes part of the URL (often called slug).
  Important page keywords should appear in the slug as well to make pages rank higher in search engines.

Use the newer haskell-actions organisation

* Revert #3639 (Don't pass -package-db and -package flags to --abi-hash)

With ghc>=9.6 `ghc --abi-hash` initialises the plugins so it will fail
if a cabal file specifies `ghc-options: -fplugin=Foo`.

Closes: #9375

* Also revert in GHC.hs

---------

Co-authored-by: Hamish Mackenzie <Hamish.K.Mackenzie@gmail.com>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

update GH validate workflow to 9.2.8, 9.4.7, 9.6.3

Bump dependencies for GHC 9.8

[cabal-7825] Implement external command system

Fix #2349 and #7825

Have hlint ignore CmmSourcesExe Demo

Avoid double space in "Executing install plan ..."

* doc: render math with HTML to make it selectable (fix #8453)

* Update doc/conf.py

Co-authored-by: Bryan Richter <bryan@haskell.foundation>

---------

Co-authored-by: Bryan Richter <bryan@haskell.foundation>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Fix markdown syntax in changelog

Create Cabal-3.10.2.1 release notes