New Release Issue - Released the library before changing the version in the library.properties

[MicroBeaut]

@ArduinoBot

[per1234]

Hi @MicroBeaut

Problem

It sounds like you have already identified the problem, but I'll provide some information. You can see the situationhere in the "MicroBeaut" library's dedicated indexer logs web page:

2022/02/24 23:22:22 Checking out tag: v1.2.0
2022/02/24 23:22:22 Release MicroBeaut:1.0.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 v1.2.0 tag (note that it checked out tag v1.2.0, but then found the release version was 1.0.0).

You can see it here:

https://github.com/MicroBeaut/MicroBeaut/blob/v1.2.0/library.properties#L2

version=1.0.0

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.

Solution

The solution is to make another release of the library which meets the requirements:

1. Update the version value in library.properties to the version that will be used for the new release.
2. Create a new release or tag in the library repository.

The indexer system will pick up that new release and it will be available from Library Manager within a day. The non-compliant release will still be missing, but since the newer release will be available, that is no problem.

Please let me know if you have any questions or concerns.
Regards, Per