Cabal revisions of Workflow-0.8.3

Hackage metadata revisions edit the .cabal file after upload; each diff below is one revision.

-
 name: Workflow
 version: 0.8.3
+x-revision: 1
 cabal-version: >= 1.6
 build-type: Simple
 license: BSD3
 license-file: LICENSE
 maintainer: agocorona@gmail.com
-stability: experimental
-bug-reports: agocorona@gmail.com
-synopsis:    Workflow patterns over a monad for thread state logging & recovery
-description: Transparent support  for interruptible computations. A workflow can be seen as a persistent thread that executes a
+stability:  experimental
+bug-reports:  agocorona@gmail.com
+synopsis: Workflow patterns over a monad for thread state logging & recovery
+description: Transparent support for interruptible computations. A workflow can be seen as a persistent thread that executes a
              monadic computation. Therefore, it can be used in very time consuming computations such are CPU intensive calculations
-             or procedures that are most of the time waiting for the action of a process or an user, that are prone to comunication
+             or procedures that are most of the time waiting for the action of a process or an user, that are prone to communication
              failures, timeouts or shutdowns. It also can be used if you like to restart your
              program at the point where the user left it last time
              .             .
              The computation can be restarted at the interrupted point thanks to its logged state in permanent storage.
              The thread state is located in files by default. It can be moved and continued in another computer.
              Besides that, the package also provides other higher level services associated to workflows: Workflow patterns,
-             and a general configuarion utility, workflow observation events and references to the internal state.
+             and a general configuration utility, workflow observation events and references to the internal state.
              The state can be stored maintaining memory references (using the "RefSerialize" package), so that it is possible to track the modifications
              of a big structure (for example a document) along the workflow execution.
              .

 name: Workflow
 version: 0.8.3
-x-revision: 1
-cabal-version: >= 1.6
+x-revision: 2
+cabal-version: >= 1.8
 build-type: Simple
 license: BSD3
 license-file: LICENSE
 
 
 library
-    build-depends: exceptions >= 0.6, RefSerialize  ,
-                   TCache , base >=4 && <5, binary , bytestring ,
-                   containers , directory -any, extensible-exceptions ,
-                    mtl , old-time , stm >2, vector
+    build-depends:
+        base >= 4 && < 4.12
+         -- GHC 8.6: "Could not deduce (Control.Monad.Fail.MonadFail STM)"
+      , binary
+      , bytestring < 0.11
+          -- bytestring-0.11 removed findSubstring
+      , containers
+      , directory
+      , exceptions >= 0.6
+      , extensible-exceptions
+      , mtl
+      , old-time
+      , stm > 2
+      , vector
+      , RefSerialize
+      , TCache
 
     exposed-modules: Control.Workflow
                      Control.Workflow.Configuration