Closed juhlig closed 3 years ago
You may remove those lines as well:
They were added exactly because 1.7 could not run on 1.8.
Also, remove this (and update CI accordingly, because with your PR tests run with test
profile would run on the same ranch version as tests run on ranch18
profile):
Other than that, I think there were some reasons why we decided to hook to ranch 1.7, but I don't remember why exactly. I'll try to find some old conversations...
Another point is that gen_smtp could work with ranch
in a quite wide range of versions: from 1.7 to 2.0. It should be possible to specify in your top-level rebar.config that your project depends on ranch 1.8
and it will override gen_smtp's 1.7
dependency specifier without any issues (not sure if it works the same in Elixir/mix)
Ok, after a bit of digging, it seems we fixed on 1.7 just because it was the most recent 1.x available by the time we bumped the version last time:
https://github.com/gen-smtp/gen_smtp/pull/218
So, I think we should we should bump to 1.8 indeed :+1: Just need to update CI and rebar.config the way I mentioned above
I agree, we can do the CI things in a separate pull request.
Merging this, as it is about OTP-24 compatibility.
Ranch 1.7 is not compatible with OTP 24 because it uses the removed function
ssl:ssl_accept
. Ranch 1.8 was released to fix this.