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
I understand this recommendation. But people using cargo-update like me would have to run cargo install-update-config --enforce-lock CRATE for every crate they install. Plus bug fixes should be installed for dependencies which is why --locked is not the default. Personally, I only use --locked if I face any issues. But again, I understand the recommendation and you don't have to deal with this if you don't want to ❤️ I just wanted to warn.
Checklist
What version of bottom are you running?
0.9.5
How did you install bottom?
cargo install bottom
without--locked
Describe the issue
When installing
bottom
usingcargo install bottom
, the installation fails after the update 0.9.5.What is the expected behaviour?
bottom
should be installed without--locked
What is the actual behaviour?
The compilation fails with the following output:
How can we reproduce this?
Run
cargo install bottom
Additional information
It works with the
--locked
flag.It should be related to pinning
serde
which is not necessary anymore as mentioned in this comment.It would be nice to revert that pinning. Thank you for developing
bottom
❤️❤️❤️The text was updated successfully, but these errors were encountered: