With recent updates of Visual Studio Code (1.17.0) and Platformio (Core 6.1.3/Home 3.4.3/IDEv2.5.1) on macOS 10.15.7 I'm experiencing strange behaviours when trying to select the Clean All project task in an environment.
Clean works fine as usual, cleaning the build directory of the environment.
Clean All however, which previously nicely also cleaned the libdeps of the project environment, now only brings up the task menu, with the shown three options when clicking on the entered Clean All command


Also when using the cli command for cleanall, e.g.
platformio run --target cleanall --environment esp32dev-ble
it cleans ALL libdeps for all previously built environments, but only the build directory for the specified environment.
I'm pretty confident that when the actual Clean All project task was still working for me previously it only ever cleared/deleted both the build directory and the libdeps only for the environment it was selected in.
Thought I had might have something messed up on my system, but just confirmed with a colleague confirming the same behaviour on his macOS 12.5 and all the latest relevant versions as myself.
With recent updates of Visual Studio Code (1.17.0) and Platformio (Core 6.1.3/Home 3.4.3/IDEv2.5.1) on macOS 10.15.7 I'm experiencing strange behaviours when trying to select the Clean All project task in an environment.
Clean works fine as usual, cleaning the build directory of the environment.
Clean All however, which previously nicely also cleaned the libdeps of the project environment, now only brings up the task menu, with the shown three options when clicking on the entered Clean All command
Also when using the cli command for cleanall, e.g.
platformio run --target cleanall --environment esp32dev-bleit cleans ALL libdeps for all previously built environments, but only the build directory for the specified environment.
I'm pretty confident that when the actual Clean All project task was still working for me previously it only ever cleared/deleted both the build directory and the libdeps only for the environment it was selected in.
Thought I had might have something messed up on my system, but just confirmed with a colleague confirming the same behaviour on his macOS 12.5 and all the latest relevant versions as myself.