library.properties linter is throwing false positives and breaking updates

[mudmin]

I've had multiple devs look at my library.properties and although the values appear to be in spec, the linter is throwing errors (LP024, LP056) and breaking my ability to update the library.

See http://downloads.arduino.cc/libraries/logs/github.com/mudmin/ESPCanary/
and
https://github.com/mudmin/ESPCanary/blob/master/library.properties

[per1234]

Hi @mudmin. The Library Manager system works from Git tags. When indexing your library, each tag is checked out and all the tags that meet the requirements are added to Library Manager. The log output shows the results of the validation at each of the tags in the history of the library repository. So this log output::

2021/10/18 22:16:01 Scraping https://github.com/mudmin/ESPCanary.git
2021/10/18 22:16:02 Checking out tag: 1.0.2
2021/10/18 22:16:02 Arduino Lint found errors:
Click to expand Arduino Lint report

Linting library in /home/ubuntu/workspace/gitclones/github.com/mudmin/ESPCanary
ERROR: library.properties author value is less than minimum length. (Rule LP024)
WARNING: The library.properties paragraph field repeats the sentence field. These are displayed together so redundancy
is not needed. (Rule LP036)
ERROR: library.properties url value is less than minimum length. (Rule LP056)
WARNING: library.properties url field value does not have a valid URL format. (Rule LP041)
WARNING: Unable to load the library.properties url field: Head "": unsupported protocol scheme "" (Rule LP042)

Linter results for project: 2 ERRORS, 3 WARNINGS

---

Linting sketch in /home/ubuntu/workspace/gitclones/github.com/mudmin/ESPCanary/examples/SimpleHoneypot

Linter results for project: no errors or warnings

---

Linter results for projects: 2 ERRORS, 3 WARNINGS

2021/10/18 22:16:02 Error syncing library: exit status 1

is the validation result at the 1.0.2 tag. If you check the library.properties file at that tag:
https://github.com/mudmin/ESPCanary/blob/1.0.2/library.properties#L8
you can see that the linter results are correct because the url field was empty at that time:

url=

The rest of the log:

2021/10/18 22:16:02 Checking out tag: v1.0.3
2021/10/18 22:16:02 Release ESPCanary:1.0.3 already loaded, skipping
2021/10/18 22:16:02 Checking out tag: v2.0.0
2021/10/18 22:16:02 Release ESPCanary:2.0.0 already loaded, skipping
2021/10/18 22:16:02 Checking out tag: v2.0.1
2021/10/18 22:16:02 Release ESPCanary:2.0.1 already loaded, skipping
2021/10/18 22:16:02 Checking out tag: v2.0.2
2021/10/18 22:16:02 Release ESPCanary:2.0.2 already loaded, skipping
2021/10/18 22:16:02 Checking out tag: v2.0.3
2021/10/18 22:16:02 Release ESPCanary:2.0.2 already loaded, skipping
2021/10/18 22:16:02 Checking out tag: v2.0.4
2021/10/18 22:16:02 Release ESPCanary:2.0.4 already loaded, skipping
2021/10/18 22:16:02 Checking out tag: v2.0.5
2021/10/18 22:16:02 Release ESPCanary:2.0.4 already loaded, skipping
2021/10/18 22:16:02 Checking out tag: v2.1.0
2021/10/18 22:16:02 Release ESPCanary:2.1.0 already loaded, skipping
2021/10/18 22:16:02 Checking out tag: v2.1.1
2021/10/18 22:16:02 Release ESPCanary:2.1.1 already loaded, skipping

Shows that all the other tags were compliant, and you can see they are all available from Library Manager:

So this problem with the library's metadata only affects one very old tag and it's likely none of the users will miss it. Other than that, there should be no problems for you to continue with the library development and distribution as always.

If you have any questions or concerns please let me know.

[mudmin]

I can't thank you enough for the detailed explanation. I had multiple devs with libraries in the IDE and none of us could figure it out. Thanks for your help!