jonathanknowles:
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?
No, 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
I 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.