Hmm, following the current phoenix guides (with phx.new for Phoenix v1.3.4)
I’m running into an issue as well. Looks like phoenix_ecto version 3.5.0 is being pulled in, even though it is listed as retired on hex: phoenix_ecto | Hex
jason@Jasons-MacBook-Pro-2 /p/t/hello> cat mix.lock |grep ecto
"ecto": {:hex, :ecto, "3.0.0", "059250d96f17f9c10f524fcb09d058f566691343e90318a161cf62a48f3912a9", [:mix], [{:decimal, "~> 1.5", [hex: :decimal, optional: false]}, {:jason, "~> 1.0", [hex: :jason, optional: true]}, {:poison, "~> 2.2 or ~> 3.0", [hex: :poison, optional: true]}]},
"phoenix_ecto": {:hex, :phoenix_ecto, "3.5.0", "f72ec302589988698c096da7e8647e917fa2bb2f861c0c3739fc9d95708bacec", [:mix], [{:ecto, "~> 2.2 or ~> 3.0", [hex: :ecto, optional: false]}, {:phoenix_html, "~> 2.9", [hex: :phoenix_html, optional: true]}, {:plug, "~> 1.0", [hex: :plug, optional: false]}]},
I would expect ecto 2.2.11 with phoenix_ecto 3.4.0 to be pulled in. Not sure what the issue is. Also not sure why I don’t get a retired package warning when I run mix deps.get.
@lorefnon thanks for bringing this up! It looks like a temporary regression because Phoenix 1.4 is in RC and a new major version of Ecto (that has some minor breaking changes) was released Yesterday. I’m sure we can get this sorted out soon.
