What a weakly worded changelog item they have published (https://monarchapp.io/blog/version-1.7.4 https://monarchapp.io/blog/version-1.7.4): > The monarch upgr

What a weakly worded changelog item they have published (https://monarchapp.io/blog/version-1.7.4 https://monarchapp.io/blog/version-1.7.4): > The monarch upgrade command used to delete old monarch files. Under certain conditions, a bug manifested where the command could delete non-monarch files. The releases where it can happen should be immediately yanked from wherever they can be downloaded, and their (Dropsource) social media should be filled with warnings not to run the `upgrade` command if they truly feel bad about deleting peoples most important files ($HOME compared to any other directory on disk). Seems they have ownership of wherever it downloads the update from "https://d2dpq905ksf9xw.cloudfront.net https://d2dpq905ksf9xw.cloudfront.net" so they can make it fail with a error message about it being unavailable, at least to stop from more people deleting files. @divan: maybe rename this submission to "WARN HN: $title" or something to make it more clear what is happening. On top of everything, it's not even clear what the problem was nor what the fix was. The authors just made a new release saying "It's fixed" without showing the patch itself. Not sure if Monarch is fully open source, but after spending 10 minutes digging through sources and releases, I can't find the place where it was adjusted to not delete all files in $HOME.