Cargo update break the package dependency

xxks-kkk · May 3, 2019, 2:58am

My project relies on nightly-2019-01-11 and I rely on package like futures-core-preview=v0.3.0-alpha12 to build. However, I run cargo update and future-core-preview has been removed and replaced with alpha 15 and all the code has been broken. I'm wondering if there is any way to force rust to use a specific package version specified in cargo.toml? Or how can I rollback the cargo update change?

My cargo.toml has something like: futures_new = { package = "futures-preview", version = "0.3.0-alpha.12"} but that is not respected in cargo build.

Thanks much for help!

RustyYato · May 3, 2019, 3:12am

If you really need a specifc version you can do something like version = '=1.0.0'. This isn't recommended for general use, but this case seems fine.

xxks-kkk · May 3, 2019, 5:05am

Thank for help! Problem solved!

system · August 1, 2019, 5:05am

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Cargo update for current cargo version help	3	287	February 19, 2023
Cargo build not using versions mentioned in cargo.toml help	4	1110	August 9, 2023
Specify the _exact_ version in Cargo? help	8	2160	January 12, 2023
No way to specify rust version in Cargo.toml?	4	4069	January 12, 2023
Best practices for bumping versions in Cargo.toml?	9	741	August 16, 2024

Cargo update break the package dependency

Related Topics