Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can we get a backport of issue 967 to the 2.0.x release? #1020

Open
telser opened this issue May 1, 2023 · 1 comment
Open

Can we get a backport of issue 967 to the 2.0.x release? #1020

telser opened this issue May 1, 2023 · 1 comment

Comments

@telser
Copy link

telser commented May 1, 2023

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.

@phadej
Copy link
Collaborator

phadej commented May 2, 2023

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants