# GHC 8.8.3 released

**URL:** <https://discourse.haskell.org/t/ghc-8-8-3-released/1115>\
**Category:** Announcements\
**Created:** [February 24, 2020, 6:13pm UTC](https://discourse.haskell.org/t/ghc-8-8-3-released/1115 "2020-02-24T18:13:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bgamari](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/bgamari/32/3599_2.png) [@bgamari](https://discourse.haskell.org/u/bgamari)\
**Post date:** [February 24, 2020, 6:13pm UTC](https://discourse.haskell.org/t/ghc-8-8-3-released/1115/1 "2020-02-24T18:13:42Z")

</div>

See [the announcement](https://www.haskell.org/ghc/blog/20200224-ghc-8.8.3-released.html) on the GHC Developer’s Blog for details.

---

<div class="post-metadata">

**Author:** ![bgamari](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/bgamari/32/3599_2.png) [@bgamari](https://discourse.haskell.org/u/bgamari)\
**Post date:** [February 24, 2020, 8:35pm UTC](https://discourse.haskell.org/t/ghc-8-8-3-released/1115/2 "2020-02-24T20:35:20Z")

</div>

Unfortunately due to a mix-up in the release process I’ve had to recall the binary distributions of this release. I’ve pulled down the binary distributions for the moment; they will be back in a few hours.

---

<div class="post-metadata">

**Author:** ![bgamari](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/bgamari/32/3599_2.png) [@bgamari](https://discourse.haskell.org/u/bgamari)\
**Post date:** [February 25, 2020, 1:43am UTC](https://discourse.haskell.org/t/ghc-8-8-3-released/1115/3 "2020-02-25T01:43:08Z")

</div>

The [issues with the release artifacts](https://gitlab.haskell.org/ghc/ghc/issues/17874) have been sorted out. Note that these are new artifacts built from [this commit](https://gitlab.haskell.org/ghc/ghc/commit/d0bab2e3419e49cdbb1201d4650572b57f33420c), which is the commit pointed to by the `ghc-8.8.3-release` [tag](https://gitlab.haskell.org/ghc/ghc/-/tags/ghc-8.8.3-release).

While we typically try hard to avoid changing artifacts after they are announced, given how quickly this issue was caught we thought this was the least bad option. Again, my apologies for the confusion and thanks for the patience.