ohhh something happened
for the first time ever cargo failed to build a rust dependency
of course it's some weird nightly codegen plugin hacky thing
i think it's rocket's 6-hour-ago release that depends on pear_codegen "0.0", but they must have changed something important between 0.0.16 and 0.0.17
cargo update fixed it
so someone messed their semver. still the best package manager
@CobaltVelvet The mess is allowing anything but a single specific version (e.g., 0.0.16 rather than 0.0) for any 0.y.z dependency. With x=0 “[a]nything may change at any time.” https://semver.org/#spec-item-4 I take that as meaning that non-backward-compatible changes are allowed on update increments.
(Yeah, people use 0. version numbers way too long.)
@edavies yeah exactly, they should have specified 0.0.17 or used 0.17 and specified the minor version
but i suspect they forgot the change was breaking or just expected people to cargo update anyway, as rocket only runs on the latest nightly and such
