For example if crate depends on some other crate via a feature - hackerman might decide to turn optional dependency into mandatory, which is fine, but if dep:used_to_be_optional_and_now_required is present - this breaks things