bump iron to 0.6

[FauxFaux]

I'm getting some weird ICE with Iron 0.6 and it's not helping having body-parser and persistent pull in iron 0.5 as well as my iron 0.6, so.. let's just upgrade everything to 0.6?

I've confirmed that this will build after the persistent change is merged, but will probably ICE or give a weird error before then:

• bump iron to 0.6 persistent#64
• beta ICE: new iron: &mut iron::Request<'_, '_> was a subtype of &mut _ but now is not? rust-lang/rust#45801

[untitaker]

Same as iron/persistent#64 (comment)

If no API changes are necessary, could you instead set this to a "range" version? I.e something like >= 0.5.0, <0.7.0

Also travis fails?

[FauxFaux]

Travis fails because it needs the persistent issue to be closed and released first.

[iori-yja]

@FauxFaux Could you change the versions of persistent if 0.4.0 has been published?
And I think it is also needed to upgrade body-parser version itself, because if the version of dependencies has been upgraded while the version itself unchanged, then user of iron-0.5.* will gets confused.

[untitaker]

Please bump persistent version

[iori-yja]

@FauxFaux Could you change the body-parser version itself? If you override the version, there might be no way to use it with iron-5.*.

[iori-yja]

And iron = "0.6" should be iron = ">= 0.5, < 0.7"

[shepmaster]

I'm getting some weird ICE

This should now be resolved in the current beta and nightly versions.

[robinst]

@untitaker I think this is good to merge and release now.

[untitaker]

Will do, thx

…

On Thu, Nov 16, 2017 at 02:54:37AM +0000, Robin Stocker wrote: @untitaker I think this is good to merge and release now. -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #79 (comment)

[robinst]

Thank you!