Skip to content

The latest version was not found in the Arduino Library Manager after the release #1552

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Tinyu-Zhao opened this issue Jul 1, 2022 · 2 comments
Assignees
Labels
conclusion: invalid Issue/PR not valid type: imperfection Perceived defect in any part of project

Comments

@Tinyu-Zhao
Copy link
Contributor

The latest version was not found in the Arduino Library Manager after the release.
I followed the tutorial to query the logs but didn't find any exceptions, please help me.
http://downloads.arduino.cc/libraries/logs/github.com/Tinyu-Zhao/M5-Depends/

@per1234 per1234 self-assigned this Jul 1, 2022
@per1234
Copy link
Contributor

per1234 commented Jul 1, 2022

Hi @Tinyu-Zhao.

Problem

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

2022/07/01 01:22:34 Checking out tag: 0.0.3
2022/07/01 01:22:34 Release M5-Depends:0.0.1 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.0.3 tag (note that the indexer checked out tag 0.0.3, only to find the release version was 0.0.1).

You can see it here:

https://github.com/Tinyu-Zhao/M5-Depends/blob/0.0.3/library.properties#L2

version=0.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.

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

@per1234 per1234 closed this as not planned Won't fix, can't repro, duplicate, stale Jul 1, 2022
@per1234 per1234 added conclusion: invalid Issue/PR not valid type: imperfection Perceived defect in any part of project labels Jul 1, 2022
@Tinyu-Zhao
Copy link
Contributor Author

Thank you for your help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conclusion: invalid Issue/PR not valid type: imperfection Perceived defect in any part of project
Projects
None yet
Development

No branches or pull requests

2 participants