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

Require hackney 1.16 #413

Merged
merged 2 commits into from
Jun 2, 2020
Merged

Require hackney 1.16 #413

merged 2 commits into from
Jun 2, 2020

Conversation

4tyTwo
Copy link
Contributor

@4tyTwo 4tyTwo commented May 26, 2020

Upgrading hackney should fix error referenced in #411 that occurs when using OTP 23

mix.exs Outdated Show resolved Hide resolved
@edgurgel edgurgel merged commit b3d57ef into edgurgel:master Jun 2, 2020
@edgurgel
Copy link
Owner

edgurgel commented Jun 2, 2020

Thanks @tcitworld & @4tyTwo ! I will release a new version soon 🎉

@tcitworld
Copy link

ping @edgurgel :)

@edgurgel
Copy link
Owner

edgurgel commented Jun 9, 2020

@tcitworld Oops! Will do later today!

BTW the way it's setup you can simply call mix deps.update hackney as semver will allow any hackney version that is not 2.0 when it's like this ~>1.15

I just did a fresh mix project and I get this:

Dependency resolution completed:
New:
  certifi 2.5.2
  hackney 1.16.0
  httpoison 1.6.2
  idna 6.0.1
  metrics 1.0.1
  mimerl 1.2.0
  parse_trans 3.3.0
  ssl_verify_fun 1.1.6

So this shouldn't be blocking anyone from getting hackney updated

@edgurgel
Copy link
Owner

v1.7.0 has been released 🎉

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

Successfully merging this pull request may close these issues.

3 participants