A breaking change was made in the 3.2.1 release of the "actions/upload-artifact" action, without doing a major version
bump as would be done in a responsibly maintained project. The action now defaults to not uploading "hidden" files.
The when the workflows fails it stores information in a file called `.check-submissions-failed`.
The `.` at the start of the `.check-submissions-failed` folder name causes it to now not be uploaded to the workflow artifact. In order
to catch such problems, the workflow configures the "actions/upload-artifact" action to fail if no files were uploaded.
So in addition to not uploading the artifact, the change in the "actions/upload-artifact" action's behavior also
resulted in the workflow runs failing:
Error: No files were found with the provided path: /home/runner/work/_temp/.check-submissions-failed. No artifacts will be uploaded.
The problem is fixed by disabling the "actions/upload-artifact" action's new behavior via the `include-hidden-files`
input. After this change, the workflow can once more upload the check-submission-failed file to a workflow
artifact as needed.
The established convention is to use the standard web URL format for the entries in the repositories.txt file.
Previously, the entry for the "K24C16 EEPROM Library" used the alternative URL format with the `.git` extension. The
Library Manage registry system is designed to support either one, so that was not a problem from a technical standpoint,
but it is better to use a consistent format throughout the file.
This library can be used to obtain the data and data fusion of MPU6050 and QMC5883L. The manufacturers of MPU6050 and QMC5883L rarely update them, which leads to the fact that many Arduino library authors no longer maintain them. However, MPU6050 and QMC5883L are still the sensors that people often come into contact with on the way of learning. In Arduino libraries, I have seen few libraries that integrate the two well. Some libraries are well written, but it is difficult for beginners to use them. So I wrote a simple to use library, in the code file also wrote more comments, easy to use and learn.
Co-authored-by: per1234 <accounts@perglass.com>
The FAQ contains an introduction to the Arduino Library Manager. This is supplemented with a list of links to references
about the Library Manager interface in each of the Arduino development tools.
The never ending churn of the Arduino IDE website structure resulted in the breakage of the link to the Arduino Cloud
reference. It is hereby updated to point to the replacement page.
