Skip to content

Conversation

MISTERNEGATIVE21
Copy link
Contributor

Ignore the old post from Main

@MISTERNEGATIVE21
Copy link
Contributor Author

@ArduinoBot

Copy link
Contributor

github-actions bot commented Oct 1, 2025

Hello! I'm checking your submission again.

@github-actions github-actions bot added the topic: other Something other than a library list request label Oct 1, 2025
Copy link
Contributor

github-actions bot commented Oct 1, 2025

Hi @MISTERNEGATIVE21.
Your pull request has been detected as something other than a Library Manager submission.
A maintainer will need to review it before it can be merged.

If you intended to submit a library, please check the instructions and update your pull request if necessary:
https://github.com/arduino/library-registry/blob/main/README.md#instructions

@github-actions github-actions bot requested a review from per1234 October 1, 2025 09:55
@per1234 per1234 added topic: rename Change registered library name and removed topic: other Something other than a library list request labels Oct 1, 2025
@per1234 per1234 self-assigned this Oct 1, 2025
Copy link
Contributor

@per1234 per1234 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @MISTERNEGATIVE21. I see you have updated the name in the library's metadata (MISTERNEGATIVE21/QuectelEC200U@496e1cb). However, Library Manager works exclusively from Git tags, so the name change won't be recognized until you create a new release or tag in the library repository.

If you look at the repository contents at the latest tag, you can see that the tagged version the Library Manager system will look at still has the old name:

https://github.com/MISTERNEGATIVE21/QuectelEC200U/blob/1.5.0/library.properties#L1

name=QuectelEC200U_CN

❗ Remember to update the value of the version property in the library's library.properties file as needed before making a release/tag.

Once you have done that, add a comment on the pull request thread to let us know we can proceed with your request.

If you have any questions or concerns, please let me know.

Regards, Per

@per1234 per1234 added the status: waiting for information More information must be provided before work can proceed label Oct 1, 2025
@per1234
Copy link
Contributor

per1234 commented Oct 1, 2025

From your other PR:

#7020 (comment)

The URL changed but its not showing the versions in Arduino Manager. I waited for 5 days

That has nothing to do with the URL change.

Problem

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

2025/10/01 15:16:52 Checking out tag: 1.3.7
2025/10/01 15:16:52 Release QuectelEC200U_CN:1.3.0 already loaded, skipping

[...]

2025/10/01 15:16:52 Checking out tag: 1.4.0
2025/10/01 15:16:52 Release QuectelEC200U_CN:1.3.0 already loaded, skipping

[...]

2025/10/01 15:16:52 Checking out tag: 1.5.0
2025/10/01 15:16:52 Release QuectelEC200U_CN:1.3.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 1.3.7, 1.4.0, and 1.5.0 tags.

For example, in this log entry:

2025/10/01 15:16:52 Checking out tag: 1.5.0
2025/10/01 15:16:52 Release QuectelEC200U_CN:1.3.0 already loaded, skipping

note that the indexer checked out tag 1.5.0, only to find the release version was 1.3.0.

You can see it here:

https://github.com/MISTERNEGATIVE21/QuectelEC200U/blob/1.5.0/library.properties#L2

version=1.3.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 to this specific problem 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.

However, in this specific case, that won't work now due to the fact that, since the time of the previous fumbled releases, you changed the library name from "QuectelEC200U_CN" to "QuectelEC200U". The Library Manager indexer rejects any release that has a different name than the name in the registry, so new releases will only be accepted after your name change request has been accommodated.

Recommendations

Since you have shown a clear pattern of forgetting to bump the version property before making a release, I recommend you write a formal release procedure for your library, and faithfully follow that procedure for all future releases.

@MISTERNEGATIVE21
Copy link
Contributor Author

I understood the issue; actually, i had changed the library properties with names and url but the thing is had to increment the version number , i kept it 1.5.0 , because i thought it would take the updated value

@per1234 per1234 removed the status: waiting for information More information must be provided before work can proceed label Oct 1, 2025
@per1234 per1234 changed the title Update registry.txt Update name of "QuectelEC200U" Oct 1, 2025
@per1234 per1234 added the status: pending backend Depends on backend maintenance operations label Oct 1, 2025
@per1234 per1234 removed their assignment Oct 1, 2025
Copy link
Contributor

@per1234 per1234 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @MISTERNEGATIVE21. I am confirming your request.

Unlike submissions, this type of request is still handled manually. The Library Manager index maintainer occasionally comes through to clear all the outstanding requests. They will merge this pull request when it is done. You will get a notification from GitHub at that time.

After that, you can monitor the indexing of the library via its dedicated logs web page.
Information about that here:
https://github.com/arduino/library-registry/blob/main/FAQ.md#can-i-check-on-library-releases-being-added-to-library-manager

@per1234 per1234 self-assigned this Oct 3, 2025
@MISTERNEGATIVE21
Copy link
Contributor Author

i guess this wont get fixed until there is manual intervention , i have fixed the version and library proterties with new version number and releaase but its not showing in arduino libraary

@MISTERNEGATIVE21
Copy link
Contributor Author

@ArduinoBot

Copy link
Contributor

github-actions bot commented Oct 5, 2025

Hello! I'm checking your submission again.

Copy link
Contributor

github-actions bot commented Oct 5, 2025

Hi @MISTERNEGATIVE21.
Your pull request has been detected as something other than a Library Manager submission.
A maintainer will need to review it before it can be merged.

If you intended to submit a library, please check the instructions and update your pull request if necessary:
https://github.com/arduino/library-registry/blob/main/README.md#instructions

@github-actions github-actions bot added topic: other Something other than a library list request and removed topic: rename Change registered library name status: pending backend Depends on backend maintenance operations labels Oct 5, 2025
@github-actions github-actions bot requested a review from per1234 October 5, 2025 18:36
@per1234 per1234 added topic: rename Change registered library name status: pending backend Depends on backend maintenance operations and removed topic: other Something other than a library list request labels Oct 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: pending backend Depends on backend maintenance operations topic: rename Change registered library name
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants