hyper build error about socket2

Yanked v0.3.13 to prevent further issues. Sorry about that!

[baoyachi]

Sometimes I think that with the semantic version of cargo, the project itself is out of control. The previous minute compiles OK, and the next minute a dependent library is updated, and some code is deleted, resulting in the project unable to compile. Is it the best choice to leave the initiative of the project to the author of the dependent project? We lost control and the project became less stable
@Keruspe

[rossmacarthur]

@baoyachi You can specify

[dependencies]
socket2 = "=0.3.12"

In your Cargo.toml until this is fixed.

[cedric-h]

Thank you! 🎉

[baoyachi]

@baoyachi You can specify

[dependencies]
socket2 = "=0.3.12"

In your Cargo.toml until this is fixed.

Thanks. I know that, but it's just a temporary solution. The problem is that our project can't be controlled normally. If we succeed in one minute, we may fail in the next. How to avoid this problem？@stjepang

[Thomasdezeeuw]

v0.3.13 and v0.3.14 are yanked and v0.3.12 should be the used version again, so this should be resolved.

[baoyachi]

Thx @Thomasdezeeuw