After doing tests with a totally clean build (running cargo clean on the workspace, deleting Cargo.lock, then running cargo test --all-features on the workspace), I was able to trace the CI failure we noticed in #398 to an unintentionally breaking change that was shipped as part of a minor version bump to an external library: https://github.com/mitsuhiko/insta/pull/385. It looks like previous versions of the _assert_serialized_snapshot macro borrowed the value, while the new one takes ownership. It is probably better for us to explicitly borrow the value here, but I'll still let them know that this change was breaking
After doing tests with a totally clean build (running
cargo clean
on the workspace, deletingCargo.lock
, then runningcargo test --all-features
on the workspace), I was able to trace the CI failure we noticed in #398 to an unintentionally breaking change that was shipped as part of a minor version bump to an external library: https://github.com/mitsuhiko/insta/pull/385. It looks like previous versions of the_assert_serialized_snapshot
macro borrowed the value, while the new one takes ownership. It is probably better for us to explicitly borrow the value here, but I'll still let them know that this change was breaking