pio update could mean it was a update one of the PIO packages, toolchain, framework or the library… unless you had the library version locked.
pio upgrade is the command that upgrades PIO itself
lib_compat_mode parameter has three options…
off (no check),
soft (default, check for compatibility with framework) and
strict (check for compatibility with framework AND platform).
So I take it what you are really asking for is for the default
soft (and strict also, for that matter) to actually show a message saying that a explicitly included library has been excluded because of the compatibility check (just so you know you’re not going completely mad?)? And probably that the
lib_compat_mode actually default to off if there’s no framework specified? Does that sound about right?
i.e. To reproduce the behaviour, with this env, PlatformIO in either the default soft or strict mode does not show the LWMQTT library (and ESPIDF framework only library) in the dependency tree, or try to compile the source code for it. But will show and compile MqttTopicHelper (Arduino framework compatible).
platform = espressif32
board = esp32cam
framework = arduino
;lib_compat_mode = strict
5671 ; LWMQTT library for ESP32 (ESP-IDF)
; 302 ; MqttTopicHelper