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
I have a project built against 0.4.2 which suddenly stopped working with compiler errors.
cargo is free to upgrade between "patch" versions, like from 0.4.2 to 0.4.5 as patch versions are not allowed to change the API. Some changes from 0.4.2 to 0.4.5 introduced API changes and should have come with an increase in the minor version number, e.g. "0.5.0".
It is too late for this now, but would be great for the future to only do API changes only via minor version number increase. More info here: https://semver.org
Workaround is to pin the version using "=0.4.2", but this is generally considered bad practice.
The text was updated successfully, but these errors were encountered:
Danvil
changed the title
0.4.5 brakes API over 0.4.2
0.4.5 breakes API over 0.4.2
Jan 26, 2024
Danvil
changed the title
0.4.5 breakes API over 0.4.2
0.4.5 breaks API over 0.4.2
Jan 26, 2024
I have a project built against 0.4.2 which suddenly stopped working with compiler errors.
cargo is free to upgrade between "patch" versions, like from 0.4.2 to 0.4.5 as patch versions are not allowed to change the API. Some changes from 0.4.2 to 0.4.5 introduced API changes and should have come with an increase in the minor version number, e.g. "0.5.0".
It is too late for this now, but would be great for the future to only do API changes only via minor version number increase. More info here: https://semver.org
Workaround is to pin the version using "=0.4.2", but this is generally considered bad practice.
The text was updated successfully, but these errors were encountered: