EOL.Wiki EOL.Wiki
← ← Back to all products

GHC

Active
Programming Languages Latest Version: 9.14.1 Latest Release: Dec 19, 2025

GHC (Glasgow Haskell Compiler) is the leading compiler and runtime for the Haskell programming language.

Versions

14

Latest Version

9.14.1

Active Support

5

EOL

9

Lifecycle Timeline

Today
9.14
9.14
9.12
9.12
9.10
9.10
9.8
9.8
9.6
9.6
9.4
9.4
9.2
9.2
9.0
9.0
8.10
8.10
8.8
8.8
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
9.14Dec 19, 2025YesNo9.14.1
Yes
Active
9.12Nov 15, 2024YesNo9.12.3No
Active
9.10May 10, 2024YesNo9.10.3No
Active
9.8Oct 9, 2023NoNo9.8.4No
Active
9.6Mar 10, 2023NoNo9.6.7No
Active
9.4Aug 7, 2022NoYes9.4.8No
EOL
9.2Oct 29, 2021NoYes9.2.8No
EOL
9.0Feb 3, 2021NoYes9.0.2No
EOL
8.10Mar 22, 2020NoYes8.10.7No
EOL
8.8Aug 25, 2019NoYes8.8.4No
EOL
8.6Sep 21, 2018NoYes8.6.5No
EOL
8.4Mar 8, 2018NoYes8.4.4No
EOL
8.2Jul 21, 2017NoYes8.2.2No
EOL
8.0May 17, 2016NoYes8.0.2No
EOL

Frequently Asked Questions

Which versions of GHC have reached end of life?
The following GHC versions have reached end of life and no longer receive security updates: 9.4, 9.2, 9.0, 8.10, 8.8, 8.6, 8.4, 8.2 (and 1 more). It is recommended to upgrade to a supported version.
Is it safe to continue using GHC 9.4?
GHC 9.4 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of GHC?
The latest version of GHC is 9.14.1, released in the 9.14 release cycle.
How many versions of GHC are currently supported?
GHC currently has 5 actively supported version(s): 9.14, 9.12, 9.10, 9.8, 9.6.
When does GHC 9.14 reach end of life?
GHC 9.14 does not have a specific end-of-life date announced yet.
What should I do when GHC reaches end of life?
When a GHC version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.