Skip to content
Snippets Groups Projects
This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. Aug 07, 2022
  2. Jun 22, 2022
    • Robert's avatar
      bootstrap: add GHC 9.0 and 9.2, and update all bootstrap files · 9e5b25ed
      Robert authored
      - parametrize the bootstrap update Makefile target to make changing
        the list of GHC versions a bit easier
      - add GHC 9.0.2 and 9.2.3 to the list of bootstrapping GHC versions
      - regenerate the bootstrapping plans across all GHC versions
      9e5b25ed
  3. May 10, 2022
  4. May 02, 2022
  5. Apr 06, 2022
  6. Feb 19, 2022
    • Andrea Bedini's avatar
      Avoid templating GitHub Actions workflow (#7952) · 65318cc6
      Andrea Bedini authored
      * Avoid templating GitHub Actions workflow
      
      GitHub Actions workflow have sufficient power to express what we need.
      We don't need to maintain and additional templating solution on top.
      
      * Add GHC 9.2, bump bounds, fix syntax
      
      * Switch to official haskell image
      
      * Always run cli tests for ghc 8.2 and above
      
      * Remove step to regenerate GitHub Actions workflows
      
      * Fix missed reference to GHC version
      
      * Fix yaml syntax
      
      * Fix type in the GHC version
      
      * More CI changes
      
      - Run bootstrap.yml on ubuntu-latest
      - Use explicit matrix for linux.yml
      - Drop containers in favour of haskell setup action
      - Drop workaround for ancient git
      
      * Remove unneeded package from CI setup
      
      I belive this is only necessary to run `cabal man` which we do not in
      the CI.
      
      * Drop old GHCs from the CI
      
      * Switch macos.yml to haskell/action/setup
      
      Also add the same GHC versions as Linux.
      
      * Simplify CI
      
      - Remove cabal-plan, we actually never call it (I think)
      - Remove vendored cabal-doctest
      - Remove few stray allow-newer clauses no longer necessary, apparently
      
      Originally done by @gbaz in PR #7907.
      
      * Mark GHC 9.2.1 as experimental
      
      * Remove reference to cabal-plan from validate.sh
      
      * setup-haskell action already runs cabal update
      
      * Add missing build matrix in test-windows-dogfood
      
      * Replace cabal-plan list-bin with cabal list-bin
      
      * Enable caching in the CI
      
      * Fix typo
      
      * Remove continue-on-error until I figure it out
      
      * Keep naming consistent
      
      * Temporarily disable 8.0.2 on macos
      
      * Add missing step id
      
      * Tweaks
      
      Remove workaround for nektos/act, it accidentally sneaked in.
      
      * More tweaks
      
      * Tweaks
      
      * Restore cabal-plan, temporarily mark everything experimental
      
      cabal list-bin doesn't seem to work like cabal-plan does.
      
      * Tweaks
      
      * Ensure cabal-plan executable gets built
      
      * Install automake on MacOS
      
      * Tweaks
      
      * Tweaks
      
      Link experimental flags to relative GitHub issues
      
      * Fix typo
  7. Feb 04, 2022
  8. Jan 26, 2022
  9. Jan 20, 2022
  10. Nov 02, 2021
    • andreas.abel's avatar
      Re #7777 #7778: check requirements.txt for security advisory · a57cbc44
      andreas.abel authored
      There is a new make file,
      
          doc/Makefile
      
      that defines these goals:
      
        - `check-requirements`:
          Check `requirements.txt` for security problems (CVEs) using `skjold`.
          This goal is intended for the "Users guide" CI.
          SKJOLD_GITHUB_API_TOKEN might have to be set if GITHUB_TOKEN is
          not in the environment, in order to access the GitHub GraphQL API.
      
        - `build-and-check-requirements`:
          Rebuild `requirements.txt` from `requirements.in` using `pip-compile`,
          and check with `check-requirements`.
          This goal is intended for manual invocation.
      
          It is invoked from the top Makefile via goal
          `users-guide-requirements`.
      
      Alternatively, these goals could be coupled with the doc build
      `make users-guide`.
      However, since these goals require a couple of seconds to run, I think
      it is annoying to call them on every build of the documentation.
      a57cbc44
  11. Sep 21, 2021
  12. Sep 17, 2021
  13. Sep 14, 2021
    • Francesco Gazzetta's avatar
      Change cabal-plan list-bin to cabal in Makefile · 42c05991
      Francesco Gazzetta authored
      cabal list-bin was introduced in cabal-install 3.4, so it's safe to
      assume every cabal developer has it by now. By using that, we
      remove the dependency on cabal-plan from the Makefile (though it's still
      present in other places).
      42c05991
  14. Sep 02, 2021
  15. Aug 05, 2021
  16. May 02, 2021
    • Emily Pillmore's avatar
      Update CI for cabal-install and cabal-install-solver · bf8dff54
      Emily Pillmore authored
      * Changes needed for GenValidate and release.py to
        accommmodate new solver dependency
      * Bumps bootstrap plans to modern GHC versions
      * Update `validate.sh` and `release.py` to accommodate new solver dep.
      * Update `Makefile` targets
      bf8dff54
  17. Nov 26, 2020
  18. Nov 03, 2020
  19. Oct 13, 2020
    • Oleg Grenrus's avatar
      Move tests from Cabal to Cabal-tests package · 579bff0c
      Oleg Grenrus authored
      The are various motivation points:
      - I'm not aware anyone third party running Cabal tests (maybe nixpkgs?)
      - No need to do gen-extra-source-files, as Cabal-tests is not distributed
      - No multiple rebuilds of Cabal-QuickCheck, Cabal-tree-diff
      - Slightly smaller Cabal sdist (which is quite big still)
      579bff0c
  20. Sep 27, 2020
  21. Sep 13, 2020
  22. Jul 22, 2020
  23. Jul 20, 2020
  24. Jul 16, 2020
  25. Jul 08, 2020
  26. Jun 13, 2020
  27. Jun 02, 2020
  28. May 18, 2020
    • Oleg Grenrus's avatar
      Make cabal-install compilable with NoImplicitPrelude · d4fd273b
      Oleg Grenrus authored
      I.e. find out where we don't yet
      used `Distribution.Client.Compat.Prelude`.
      
      - If the module is small I added direct `Prelude` imports.
      - Add Exception, deepseq stuff to Cabal Prelude
      - Add Parsec, Pretty and Verbosity to Client Prelude
      - use for, for_, traverse and traverse_ (removes need for Control.Monad)
      d4fd273b
  29. May 15, 2020
Loading