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
webp bumped its dependency on image from ^0.24 to ^0.25, which are semver incompatible releases, and it did so in a semver compatible release of webp from 0.2.6 to 0.2.7, which is incorrect. Bumping the version of a public dependency to a semver-incompatible version is a breaking change and should be reflected in the versioning of this crate.
Commit in which image's version was bumped in webp: 5596534
For additional context, i encountered this issue while running cargo install --git https://github.com/getzola/zola --tag v0.18.0, which uses webp = "0.2" as dependency; because there was no bump in the minor version number, their builds suddenly break if you remove the lock file (or ignore it as cargo build does by default).
This problem was discovered by @Lymkwi.
webp
bumped its dependency onimage
from^0.24
to^0.25
, which are semver incompatible releases, and it did so in a semver compatible release ofwebp
from0.2.6
to0.2.7
, which is incorrect. Bumping the version of a public dependency to a semver-incompatible version is a breaking change and should be reflected in the versioning of this crate.image
's version was bumped inwebp
: 5596534DynamicImage
fromimage
appears in the public API ofwebp
and is defined in version0.24.7
ofimage
DynamicImage
fromimage
now links to version0.25.1
ofimage
, which is semver incompatible with0.24.7
I imagine a fix for this problem would be to yank
0.2.7
ofwebp
and rerelease it as0.3.0
.The text was updated successfully, but these errors were encountered: