I recently had the incident that I renamed a launch file file.launch from pkg1 and went on to merge my branch because everything was working fine. But of course it didn't. The problem was that renamed file.launch file was used by a robot bringup package pkg2 where the changes what file to include were not yet merged yet. However that file even when deleted, will stay in catkinws/install which leads to confusion when testing. Even worse, after cleaning the catkinws for testing again, ros will automatically fallback to the launch file of an older version of the same package pkg1 that was installed using apt-get. Only when I sudo delete that file in /opt/ros/melodic/share/pkg1/file.launch I get the failing bringup.

How do you guys handle these cases? Will ROS2 display warnings if that happens?