iridium: Automated Local Cabal Package Testing and Uploading

[ bsd3, development, library, program ] [ Propose Tags ]

This executable aims to automate several typical steps when uploading a new package version to hackage.

Steps currently include:

The program is configurable using a per-project .yaml file.

See the README.

[Skip to Readme]
Versions [RSS] [faq],,,,,,,
Change log
Dependencies aeson (==1.4.*), ansi-terminal (>= && <0.7), base (>=4.8 && <4.11), bytestring (>= && <0.11), Cabal (>= && <1.25), containers (>= && <0.6), extra (>=1.4.3 && <1.7), foldl (>=1.1.5 && <1.3), HTTP (==4000.3.*), iridium, lifted-base (>= && <0.3), monad-control (>= && <1.1), multistate (>= && <0.8), network-uri (==2.6.*), process (>= && <1.5), split (>=0.2.3 && <0.3), system-filepath (>= && <0.5), tagged (>=0.8.3 && <0.9), text (>= && <1.3), transformers (>= && <0.6), transformers-base (>=0.4.4 && <0.5), turtle (>=1.3.0 && <1.4), unordered-containers (>= && <0.3), vector (>= && <0.13), yaml (>=0.8.16 && <0.9) [details]
License BSD-3-Clause
Copyright Copyright (C) 2016 Lennart Spitzner
Author Lennart Spitzner
Maintainer Lennart Spitzner <>
Category Development
Home page
Bug tracker
Source repo head: git clone
Uploaded by lspitzner at 2018-10-03T13:11:01Z
Distributions NixOS:
Executables iridium
Downloads 4381 total (35 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Hackage Matrix CI
Docs uploaded by user
Build status unknown [no reports yet]




Maintainer's Corner

For package maintainers and hackage trustees


Readme for iridium-

[back to package description]


Build Status Hackage


iridium is a fancy wrapper around cabal upload. It aims to automate several typical steps when releasing a new package version to hackage.

Iridium does all testing locally, in contrast to e.g. github's travis. This makes it easier to keep your published history free of commits that fail any tests (without squashing or separate branches).

Steps currently include:

  • Compilation and running tests using multiple compiler versions. (the different compilers must already be installed.)

  • Checking that the changelog mentions the latest version.

  • Checking that the upper bounds of dependencies are up-to-date by making use of stackage snapshots.

  • Uploading of both the package itself and the documentation.

The output on errors is certainly not optimal; for example the stackage upper bound checking will print a typical, hard-to-consume cabal error message. iridium's focus is on notifying if something is wrong.


Install iridium, run iridium in the directory containing the cabal package. It won't do anything without confirmation.

$ iridium
Checking compilation with different compiler versions
  Checking with compiler ghc-7.8.4:                                   clear.
Checking upper bounds using stackage:                                 clear.
Checking documentation:                                               clear.
Checking basic compilation:                                           clear.
Checking that all dependencies have a lower bound:                    clear.
Checking that all dependencies have an upper bound:                   clear.
Checking package validity:                                            clear.
Testing the source distribution package:                              clear.
Testing if the changelog mentions the latest version:                 clear.
Comparing local version to hackage version:                           clear.
  Testing for uncommitted changes:                                    clear.
  Package:                iridium
  Warning count:          0
  Error   count:          0
  Not -Wall clean:        []
    Branch:               master
  Actions:                Tag the current commit with ""
                          Push current branch and tag to upstream repo
                          Upload package
                          Upload documentation
> Continue [y]es [n]o? > y
Performing upload..
Building source dist for iridium-
Preprocessing library iridium-
Preprocessing executable 'iridium' for iridium-
Source tarball created: dist/iridium-
Hackage password:
Uploading dist/iridium-
Upload successful.
Performing doc upload..
[.. some haddock spam ..]
Documentation tarball created: dist/iridium-
Hackage password:
Uploading documentation dist/iridium-
Documentation upload successful.


An iridium.yaml file will be created on first invocation.


Test Description
hlint forM_ hs-source-dirs $ \dir -> (\dir -> call "hlint " ++ dir)
testsuites run cabal test when compiling.
upper-bounds-stackage Check that upper bounds are up-to-date by using a stackage cabal.config. This is not the best way, because not all packages are on stackage, but it is better than nothing.
lower-bounds-exist Check that all dependencies have a lower bound.
upper-bounds-exist Check that all dependencies have an upper bound. (You do want to conform with the PVP, right?)
documentation Check that haddocks can be created without problems (calling cabal haddock).
changelog Check if the changelog mentions (contains) the latest version.
package-sdist Check that all necessary stuff is contained in the source distribution by installing the packaged package.
compiler-versions Compile and run tests for several compiler versions (other than the default compiler on $PATH).