To clarify, if reqwest were v1.2.3, I'd expect new features requiring a newer compiler to make it v1.3, not v2.0. So the equivalent means v0.9.6, not v0.10.
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I would argue that as it would no longer compile (I am assuming) on an older version that it would be breaking for those users and as such should be a breaking change
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
It is a breaking chance since it won't compile on an older version
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
That’s a breaking change.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I agree that it is a patch.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Patch & use edition = 2018 in Cargo.toml in the new reqwest version & add info to README or patch & gate it w/ cfg(feature_available(...))?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I tend to do breaking change and write a change log clarifying what, if any, changes downstream users must make.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
There is no correct answer... but as a datapoint all my libs that depend on reqwest are quite high-level and target 'latest stable' already
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
If not a major bump, I would go with at least a minor bump. Patch seems too small for a change like that.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
breaking change. It’s better patches don’t break things.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.