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

Cut 4.0 release #94

Open
yurrriq opened this issue Nov 25, 2020 · 7 comments · May be fixed by #102
Open

Cut 4.0 release #94

yurrriq opened this issue Nov 25, 2020 · 7 comments · May be fixed by #102
Labels

Comments

@yurrriq
Copy link
Member

yurrriq commented Nov 25, 2020

Depends on #93, at least. This is just a reminder for now.

@yurrriq yurrriq mentioned this issue Feb 2, 2021
@yurrriq yurrriq added the 4.0 label Feb 2, 2021
@yurrriq yurrriq linked a pull request Feb 2, 2021 that will close this issue
@paulo-ferraz-oliveira
Copy link
Contributor

@tsloughter, this is now around 4 years old 😄 I love my Elli and would like to see a 4.0 too. Anything I can do to help move it forward? Triage some more issues, fix some more stuff, close some more issues (?)

@tsloughter
Copy link
Member

Do you know what the breaking changes are that make this 4.0?

@paulo-ferraz-oliveira
Copy link
Contributor

paulo-ferraz-oliveira commented Jul 10, 2024

I can look at the commits since the last release.

Edit: fwiw, 3.3.0...main.

@paulo-ferraz-oliveira
Copy link
Contributor

This is what I found:

  • record req now has field original_headers (was parsed_headers during dev.)
    • this is mentioned in the CHANGELOG
  • header names are downcased (though this is most likely not breaking)
  • the min. supported OTP bumped to 24+

@paulo-ferraz-oliveira
Copy link
Contributor

This draft also seems to mention some stuff that could be included in the next major, but that shouldn't prevent 4.x from being released.

@yurrriq
Copy link
Member Author

yurrriq commented Sep 26, 2024

I'm pretty busy for the next two months, but usually try to do fun stuff like this during December. No need to wait for me, but I'm saying I could commit to helping out then. In the meantime I'm happy to review PRs or just be a cheerleader.

@paulo-ferraz-oliveira
Copy link
Contributor

@yurrriq, given your comment, I think the following could benefit from a review and/or follow-up:

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

Successfully merging a pull request may close this issue.

3 participants