Per Tillisch

@ianfixes do you agree with my previous statement?: >The creation of the CI configuration file and which tests will be done on the library will be up to the library...

>Why not? Anyone can select a widely used board, manually open each of library's examples and click Verify. Why can't a CI script do the same? Many libraries/examples are written...

>I'm pretty sure that the question of using a dependency manager should be opened. It already has: - https://github.com/arduino/Arduino/issues/8323 - https://github.com/arduino/Arduino/issues/5795 >I just don't really know why we couldn't have...

I think PaulStoffregen has a very interesting idea. The way I see it working is for Arduino to provide this as a "hardware-in-the-loop" testing service. They maintain a room full...

There is, in my opinion, another small step forward in this effort today. As I mentioned above, the Arduino Library Manager system already does some basic checks on the library...

Related Boards Manager issue: https://github.com/arduino/arduino-ide/issues/1493

@JarekParal since it appears you don't use the official Arduino development software and thus won't be able to manually detect the introduction of changes that break the library for users...

Hi @VojtechBartoska. Unfortunately yes it still is. **`@me-no-dev`** did an investigation and reported the findings here: https://github.com/arduino/arduino-ide/issues/740#issuecomment-1086595394

Thanks for your suggestion @zsoltyfm. As you are aware, there is already a request for TCP support: https://github.com/arduino-libraries/ArduinoModbus/issues/123 so this request is redundant in that respect. I am not knowledgeable...

I think the need for this capability is even greater now that multiple uploads to a single artifact via **actions/upload-artifact** is no longer allowed: https://github.com/actions/upload-artifact#breaking-changes Previously, many of my workflows...