How do I figure out dependency version bounds for my library (when publishing on Hackage)?

1. strong-path

   1 2 16 2.3 Haskell

   Strongly typed paths in Haskell

   

   I wrote a strong-path package, which I published on Hackage. I am using Stack to build it: I have stack.yaml and package.yaml as sources of truth, while strong-path.cabal is generated by Stack but I also commit it into vcs.

2. AppSignal

   www.appsignal.com sponsored

   AppSignal knows why the f*#k it crashed. Stop vibe-debugging. Every exception, every backtrace, grouped so you see patterns, not noise.

   

3. semver

   2 820 7,862 2.1

   Semantic Versioning Specification

   

   It sounds like you are writing about SemVer. Hackage packages use PVP - Package Version Policy in which the first two components of a version number denote the major version.

4. cabal-install-parsers

   3 3 454 5.6 Haskell

   Scripts and instructions for using CI services (e.g. Travis CI or Appveyor) with multiple GHC configurations

   

   If you're on github, I'd look at https://github.com/haskell-CI/haskell-ci , which generates a GH actions template from the tested-with: fields in the cabal file.

Suggest a related project