Skip to content

New version not showing up #3090

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
tedtoal opened this issue Jul 18, 2023 · 1 comment
Closed

New version not showing up #3090

tedtoal opened this issue Jul 18, 2023 · 1 comment
Assignees
Labels
conclusion: invalid Issue/PR not valid topic: other Something other than a library list request type: imperfection Perceived defect in any part of project

Comments

@tedtoal
Copy link
Contributor

tedtoal commented Jul 18, 2023

My library, monitor_printf, released the initial time with V1.1.1, but subsequent versions do not. The log shows:

2023/07/18 12:29:43 Scraping https://github.com/tedtoal/monitor_printf.git
2023/07/18 12:29:43 Checking out tag: V1.1.1
2023/07/18 12:29:43 Release monitor_printf:1.1.1 already loaded, skipping
2023/07/18 12:29:43 [Arduino Lint](https://arduino.github.io/arduino-lint/latest/) has suggestions for possible improvements:
Click to expand Arduino Lint report

2023/07/18 12:29:43 Checking out tag: V1.2.1
2023/07/18 12:29:43 Release monitor_printf:1.1.1 already loaded, skipping
2023/07/18 12:29:43 [Arduino Lint](https://arduino.github.io/arduino-lint/latest/) has suggestions for possible improvements:
Click to expand Arduino Lint report

2023/07/18 12:29:43 Checking out tag: V1.3.1
2023/07/18 12:29:43 Release monitor_printf:1.1.1 already loaded, skipping
2023/07/18 12:29:43 [Arduino Lint](https://arduino.github.io/arduino-lint/latest/) has suggestions for possible improvements:
Click to expand Arduino Lint report

2023/07/18 12:29:43 Checking out tag: V1.4.1
2023/07/18 12:29:43 Release monitor_printf:1.4.1 already loaded, skipping
2023/07/18 12:29:43 Checking out tag: V1.5.1
2023/07/18 12:29:43 Release monitor_printf:1.5.1 already loaded, skipping

The V1.3.1 release I made specifically to try to get it to update, making no changes other than updating the release number library.properties and then creating the release and the tag V1.3.1.

I have not renamed the library.

Why is it not creating new releases?

@per1234 per1234 self-assigned this Jul 18, 2023
@per1234 per1234 transferred this issue from arduino/Arduino Jul 18, 2023
@per1234 per1234 added the type: imperfection Perceived defect in any part of project label Jul 18, 2023
@per1234
Copy link
Contributor

per1234 commented Jul 18, 2023

Hi @tedtoal.

The problem is shown here in the logs:

2023/07/18 12:29:43 Checking out tag: V1.2.1
2023/07/18 12:29:43 Release monitor_printf:1.1.1 already loaded, skipping
2023/07/18 12:29:43 [Arduino Lint](https://arduino.github.io/arduino-lint/latest/) has suggestions for possible improvements:
Click to expand Arduino Lint report

2023/07/18 12:29:43 Checking out tag: V1.3.1
2023/07/18 12:29:43 Release monitor_printf:1.1.1 already loaded, skipping
2023/07/18 12:29:43 [Arduino Lint](https://arduino.github.io/arduino-lint/latest/) has suggestions for possible improvements:
Click to expand Arduino Lint report

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.1 and V1.3.1 tags (note that the indexer checked out tag V1.2.1, only to find the release version was 1.1.1, and the same when checking out the V1.3.1).

You can see it here:

https://github.com/tedtoal/monitor_printf/blob/V1.2.1/library.properties#L2

version=1.1.1

https://github.com/tedtoal/monitor_printf/blob/V1.3.1/library.properties#L2

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


I see you have already followed the correct procedure when making the 1.4.1 and 1.5.1 releases, and that those have already been indexed by the Library Manager system, so no action is needed. Just be very careful to follow the correct procedure when making future releases of your library.

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 topic: other Something other than a library list request type: imperfection Perceived defect in any part of project
Projects
None yet
Development

No branches or pull requests

2 participants