Hey @benbass 👋, historically osquery itself hasn't provided any mechanism to do that -- it relied on however folks deployed osquery across their fleet (chef/mdm/etc). I guess it just worked out that way because all the paths, identifiers (com.facebook.osquery), etc were the same for, and macOS installer just replaces the binary.
Now with the change in identifiers, code signatures, paths and app bundle, it is expected that whatever osquery is deployed with, it manages stopping the old version. This can certainly be better documented and highlighted! I will also bring this up in #officehours tomorrow, and see what other folks think and whether going forward, we can include a preflight script of sorts