Supported GHC Versions¶
Déjà Fu supports the latest four GHC releases, at least. For testing purposes, we use Stackage LTSes as a proxy for GHC versions. The currently supported versions are:
In practice, we may compile with older versions of GHC, but keeping them working is not a priority.
Adding new GHC releases¶
When a new version of GHC is released, we need to make some changes for everything to go smoothly. In general, these changes should only cause a patch level version bump.
- Bump the upper bound of base and set up any needed conditional compilation
- Add the GHC and base versions to the table.
- Remove any unsupported versions from the table.
- Make a patch release.
A new GHC release won’t get a Stackage LTS for little while. When it does:
- Add the LTS to the GitHub Actions configuration.
- Update the resolver in the stack.yaml.
- Put the LTS in the table.
Dropping old GHC releases¶
When we want to drop an unsupported version of GHC, we need to bump the version bound on base to preclude it. This is a backwards-incompatible change which causes a major version bump.
- Remove the dropped GHC version from the GitHub Actions configuration.
- Bump the lower bound of base.
- Look through the other dependencies. Some may not work with our new lower bound on base, so we should bump those too.
- Remove any now-irrelevant conditional compilation (mostly CPP, but there may also be some cabal file bits).
- Make whatever change required the bump.
- Make a major release.
GHC versions shouldn’t be dropped just because we can, but here are some good reasons to do it:
- We want to bump the lower bounds of a dependency to a version which doesn’t support that GHC.
- We want to add a new dependency which doesn’t support that GHC.
- The conditional compilation needed to keep that GHC working is getting confusing.