A package bundled with the upcoming GHC 8.2.1 RC1 (and exposed via ghc-pkg list) shall either
have its submodule point to the commit matching an existing release on Hackage, or
point to the commit representing the unreleased release-candidate state planned for inclusion in GHC 8.0.1
In the latter case, the unreleased candidate's advertised package version number shall be distinct from any officially released package version available on Hackage, and have the appropriate version bump according to the PVP (i.e. patch-level, minor, or major) relative to previous releases.
For GHC 8.2.1 final
All ghc-pkg-exposed packages must match their officially released Hackage release.
3rd Party Packages needing a release (candidate)
GHC HQ controlled base/array/integer-gmp/template-haskell/etc. are not listed here
The git describe-version reported in brackets (e.g. (v0.5.1.0-7-g4b43c95)) tells us whether a commit points to an annotated Git tag (and thus most likely corresponds to a released package version). Version descriptions with ah -g[0-9a-f]+ suffix denote commits in between Git tags!