Skip to content

[Library Manager] lib update version issues #987

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
Gitshaoxiang opened this issue Jan 28, 2022 · 1 comment
Closed

[Library Manager] lib update version issues #987

Gitshaoxiang opened this issue Jan 28, 2022 · 1 comment
Assignees
Labels
conclusion: invalid Issue/PR not valid type: imperfection Perceived defect in any part of project

Comments

@Gitshaoxiang
Copy link
Contributor

Hi. we just update try to release a new tag & version.
I have tried to delete the tag and release it again. but seems it still can't update.
could you help me check this problem?

M5EPD LIB LINK
M5Atom LIB LINK

image

image

@Gitshaoxiang Gitshaoxiang changed the title [Library Manager] M5EPD lib update version issues [Library Manager] lib update version issues Jan 28, 2022
@per1234
Copy link
Contributor

per1234 commented Jan 28, 2022

Hi @Gitshaoxiang

Problems

The problem in the "M5EPD" library's logs:

2022/01/28 02:18:49 Checking out tag: 0.1.2
2022/01/28 02:18:49 Release M5EPD:0.1.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.1.2 tag.
You can see it here:
https://github.com/m5stack/M5EPD/blob/0.1.2/library.properties#L2

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


The problem is the same for the "M5Atom" library:

2022/01/28 03:13:57 Checking out tag: 0.0.8
2022/01/28 03:13:57 Release M5Atom:0.0.7 already loaded, skipping

https://github.com/m5stack/M5Atom/blob/0.0.8/library.properties#L2

version=0.0.7

Solution

The solution is to make another release of each library which meet 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, it is no problem.

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

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