{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiafjzvwqia5du5bc2uxnzagxz24eae7sd4636i5umuuwnvmt3pbhu",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mnqcffhcnlq2"
  },
  "path": "/t/looking-for-a-parsec-maintainer-to-assist-with-ghc-9-14-compatibility-is-this-package-still-actively-maintained/14191#post_7",
  "publishedAt": "2026-06-07T21:24:03.000Z",
  "site": "https://discourse.haskell.org",
  "tags": [
    "@bgamari",
    "Bump base upper bound to <4.23 by bgamari · Pull Request #193 · haskell/parsec · GitHub"
  ],
  "textContent": "jonathanknowles:\n\n> It seems like the process expects these changes to be propagated back at release time, and that this step was missed for GHC `9.14.1`. Is that right?\n\nNo, it seems a GHC maintainer (@bgamari) opened a PR against the `parsec` repository well in advance of the 9.14.1 release: Bump base upper bound to <4.23 by bgamari · Pull Request #193 · haskell/parsec · GitHub\n\nI don’t know why this wasn’t merged, but unfortunately since `parsec` is a boot library and its constraints need to be consistent with the version of `base` released with GHC, the GHC maintainers wouldn’t have had another option but to distribute GHC with a patched `parsec`. In this case the immediate fix is to revise the package bounds, but it does seem like a new maintainer for `parsec` might be appropriate.",
  "title": "Looking for a parsec maintainer to assist with GHC 9.14 compatibility (is this package still actively maintained?)"
}