Fix cabal check output - #6

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Top-level binding with no type signature:

Top-level binding with no type signature:

Top-level binding with no type signature:

Top-level binding with no type signature:

Top-level binding with no type signature:

Top-level binding with no type signature: resChkConfig :: Args

Top-level binding with no type signature: solveConfig :: Args

Top-level binding with no type signature: config :: Args

The qualified import of ‘Data.Foldable’ is redundant

Module ‘Funsat.Solver’ does not export ‘(==>)’.

Module ‘Control.Monad.Except’ does not export ‘forM_’.

Module ‘Control.Monad.Except’ does not export ‘(>=>)’.

In the use of ‘tail’

• The constraint ‘MArray (STArray s) e (ST s)’ matches

Module ‘Control.Monad.State.Lazy’ does not export ‘forM_’.

Module ‘Control.Monad.State.Lazy’ does not export ‘(>=>)’.

In the use of ‘tail’

• The constraint ‘MArray (STArray s) e (ST s)’ matches

Module ‘Control.Monad.State.Lazy’ does not export ‘forM_’.