New library releases ignored

[erropix]

My library https://docs.arduino.cc/libraries/esp32-analogwrite/ was updated in the library manager since the first release.

I checked the logs file https://downloads.arduino.cc/libraries/logs/github.com/erropix/ESP32_AnalogWrite and it wasn't found.

What is the issue preventing new releases from being picked?

[per1234]

I checked the logs file https://downloads.arduino.cc/libraries/logs/github.com/erropix/ESP32_AnalogWrite and it wasn't found.

You forgot to add the trailing slash to the URL. You can see the logs here:

https://downloads.arduino.cc/libraries/logs/github.com/ERROPiX/ESP32_AnalogWrite/

What is the issue preventing new releases from being picked?

Problem

You can see the problem in the logs page:

2025/05/22 14:20:13 Checking out tag: 0.2
2025/05/22 14:20:13 Release ESP32 AnalogWrite:0.1.0 already loaded, skipping

Unfortunately, the logs don't communicate about this particular thing very well, but what this tells us is that the version value in the library.properties metadata file was not updated before creating the 0.2 tag (note that the indexer checked out tag 0.2, only to find the release version was 0.1.0).

You can see it here:

https://github.com/erropix/ESP32_AnalogWrite/blob/0.2/library.properties#L2

version=0.1

Even though Git tags are the unit of release for the Arduino Library Manager, all versioning is done according to the version field of the library.properties file.

For this reason, the indexer will reject any tag that has the same value in its version field as a release already in the index.

I see that you followed the correct release procedure when you made the 0.3 tag an hour ago. It takes some time for the new release to work through the cache to be visible in everyone's Library Manager. I can already see it in mine, but it might not be present in yours yet. We give a conservative estimate of universal availability within a days time.

[erropix]

@per1234 thank you so much for the details, the issue was resolved now