Libraries not updating after a release

[sbarabe]

I'm sorry to bug you with that because I know that there are detailed information about this, but I don't get it. It seems to me I do it right but registry update is skipping my releases for 2 libraries:

• https://github.com/sbarabe/SBK_BarDrive
• https://github.com/sbarabe/SBK_MAX7219

Can you assist me ?

I've the library properties files with the release version, names seem the same, tags and releases are pushed on github...

This is what I get from the logs:

2025/11/19 13:16:17 Scraping https://github.com/sbarabe/SBK_BarDrive.git
2025/11/19 13:16:17 Checking out tag: 1.0.0
2025/11/19 13:16:17 Release SBK_BarDrive:1.0.0 already loaded, skipping
2025/11/19 13:16:17 Checking out tag: 1.0.1
2025/11/19 13:16:18 Release SBK_BarDrive:1.0.1 already loaded, skipping
2025/11/19 13:16:18 Checking out tag: 1.0.2
2025/11/19 13:16:18 Release SBK_BarDrive:1.0.2 already loaded, skipping
2025/11/19 13:16:18 Checking out tag: 2.0.0
2025/11/19 13:16:18 Release SBK_BarDrive:2.0.0 already loaded, skipping
2025/11/19 13:16:18 Checking out tag: 2.0.1
2025/11/19 13:16:18 Release SBK_BarDrive:2.0.0 already loaded, skipping

2025/11/19 13:16:18 Scraping https://github.com/sbarabe/SBK_MAX72xx.git
2025/11/19 13:16:18 Checking out tag: 1.0.0
2025/11/19 13:16:18 Release SBK_MAX72xx:1.0.0 already loaded, skipping
2025/11/19 13:16:18 Checking out tag: 2.0.0
2025/11/19 13:16:18 Release SBK_MAX72xx:2.0.0 already loaded, skipping
2025/11/19 13:16:18 Checking out tag: 2.0.1
2025/11/19 13:16:18 Release SBK_MAX72xx:2.0.0 already loaded, skipping

[per1234]

Hi @sbarabe

Problem

The problem is shown here in the logs:

2025/11/19 13:16:18 Checking out tag: 2.0.1
2025/11/19 13:16:18 Release SBK_BarDrive:2.0.0 already loaded, skipping

2025/11/19 13:16:18 Checking out tag: 2.0.1
2025/11/19 13:16:18 Release SBK_MAX72xx:2.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 2.0.1 tags in the library repositories (note that the indexer checked out tag 2.0.1, only to find the release version was 2.0.0).

You can see it here:

https://github.com/sbarabe/SBK_BarDrive/blob/2.0.1/library.properties#L2

version=2.0.0

and here:

https://github.com/sbarabe/SBK_MAX72xx/blob/2.0.1/library.properties#L2

version=2.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 each of the libraries 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.

Additional context

As for the other log entries, such as this one:

2025/11/19 13:16:17 Checking out tag: 1.0.0
2025/11/19 13:16:17 Release SBK_BarDrive:1.0.0 already loaded, skipping

these are normal and expected. The indexer checks out each of the tags in the library repository, as shown by log entries like this:

2025/11/19 13:16:17 Checking out tag: 1.0.0

and checks to see if a release of the library with the version number provided in the library's metadata has already been added to the Arduino Library Manager. If it finds that there is already a release with that version number, it skips adding the release, as shown by log entries like this:

2025/11/19 13:16:17 Release SBK_BarDrive:1.0.0 already loaded, skipping

So you only need to worry about seeing these "skipping" log entries in the case where you do not find the expected releases in Library Manager.

---

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

Regards, Per

[sbarabe]

Ok it works. I'll correct my procedure, I was creating tag and release before pushing the update.code and files to github...

Thanks for the follow-up!

Samuel