Update repositories.txt

[Init-io]

New library update

[per1234]

@ArduinoBot please check the PR.

[github-actions]

Hello! I'm checking your submission again.

[github-actions]

A problem was found with your submission https://github.com/Init-io/FireEsp

❌ ERROR: Submission URL is already in the Library Manager index.

[github-actions]

Thanks for your interest in contributing to the Arduino Library Manager index @per1234
Please resolve the error(s) mentioned in the previous comment.

After resolving the issue, trigger this check again by doing one of the following:

• Commit the required change to the branch you submitted this pull request from.
• Comment here, mentioning @ArduinoBot in the comment.

❗ NOTE: It is not necessary to open a new pull request. ❗

More information:
https://github.com/arduino/library-registry/blob/main/README.md#if-the-problem-is-with-the-pull-request

[per1234]

Closing as duplicate of #5454

[Init-io]

my library version isn't updating in Arduino IDE

[per1234]

Hi @Init-io.

Problem

The problem is shown here in the "FireEsp" library's dedicated indexer logs web page:

2025/06/22 07:09:20 Checking out tag: 1.1.3
2025/06/22 07:09:20 Release FireEsp:1.0.2 already loaded, skipping
2025/06/22 07:09:20 Checking out tag: 1.2.0
2025/06/22 07:09:20 Release FireEsp:1.0.2 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 1.1.3 and 1.2.0 tags (note that the indexer checked out tag 1.2.0, only to find the release version was 1.0.2).

You can see it here:

https://github.com/Init-io/FireEsp/blob/1.2.0/library.properties#L2

version=1.0.2

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