You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The HF Stability Working Group discussed the TH fix and the impact to the community.
For clarity, I'm talking about this commit 720b857 specifically.
It would seem that the current stackage LTS would benefit from this fix, as it seems risky to them to bump to the 2.1.x, given this conversation commercialhaskell/stackage#6905.
The text was updated successfully, but these errors were encountered:
2.0.3.0 was released on 2022-01-01T16:41:29Z (16 months ago)
2.1.0.0 was released on 2022-06-15T14:07:42Z (11 months ago)
I don't understand why aeson-2.1 weren't in LTS-20, which 20.0 was published on 2022-11-16, i.e. five months after 2.1.0.0 was released, and two months after 2.1.1.0 (published on 2022-09-21T15:17:01Z).
Stackage team included into LTS known to be broken aeson release. Why it's an issue now, but wasn't then?
The HF Stability Working Group discussed the TH fix and the impact to the community.
For clarity, I'm talking about this commit 720b857 specifically.
It would seem that the current stackage LTS would benefit from this fix, as it seems risky to them to bump to the 2.1.x, given this conversation commercialhaskell/stackage#6905.
The text was updated successfully, but these errors were encountered: