73104e5803
A [patch.crates-io] whose version doesn't satisfy the dependency
requirement is silently IGNORED by cargo — it emits a warning ('patch was
not used in the crate graph') and builds against the real crates.io crate
instead. The 1.0.10-alpha release build hit exactly this: the fork's
version bump to 0.33.3 had never been committed, so CI cloned 0.33.2, the
patch was dropped, and the build failed four minutes later with 'cannot
find type CursorImage' in a file that had nothing to do with the cause.
The one line that explained it was scrolled far above the errors.
Check for the warning right after cloning the fork and fail there, naming
both versions.
|
||
|---|---|---|
| .. | ||
| workflows | ||