You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: text/3493-precise-pre-release-cargo-update.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -124,6 +124,14 @@ This would allow any version to masquerade as another.
124
124
Without the concept of compatible pre-releases there would be no path forward towards being able to express pre-release requirements in library crates.
125
125
This is explored in [future-possibilities].
126
126
127
+
## Change the version in `Cargo.toml` rather than `Cargo.lock` when using `--precise`
128
+
129
+
This [accepted proposal](https://github.com/rust-lang/cargo/issues/12425) allows cargo to update a projects `Cargo.toml` when the version is incompatible.
130
+
131
+
The issue here is that cargo will not unify a pre-release version with a stable version.
132
+
If the crate being updated is used pervasively this will more than likely cause a resolver error.
133
+
This makes this alternative unfit for our [motivation].
134
+
127
135
## Pre-releases in `Cargo.toml`
128
136
129
137
Another alternative would be to resolve pre-release versions in `Cargo.toml`s even when another dependency specifies a stable version.
0 commit comments