This primarily forces the compilation tests to use the esp32 library at version 2.0.17 until such time that the other libraries catch up to changes from the new v3.0.0 release. The newest seems to cause some issues with our required libraries (as best I can tell) but seems the devs are aware and working on it...I hope.
In the meantime, if using Arduino IDE do not let it update to the latest espressif/arduino-esp32 library or your compiles will fail there as well. That change is more impactful to building of the binaries, while the compile-test.yml is just a sanity check.
This primarily forces the compilation tests to use the esp32 library at version 2.0.17 until such time that the other libraries catch up to changes from the new v3.0.0 release. The newest seems to cause some issues with our required libraries (as best I can tell) but seems the devs are aware and working on it...I hope.
In the meantime, if using Arduino IDE do not let it update to the latest espressif/arduino-esp32 library or your compiles will fail there as well. That change is more impactful to building of the binaries, while the compile-test.yml is just a sanity check.