Library release removal request

[TanishKunthe]

Library name

LF_Alpha

Version to remove

1.0.0

[per1234]

The release removal service is provided by Arduino for emergencies where some content that absolutely must not be published (e.g., a copyright violation) was accidentally included in a release. If such an emergency has occurred then we are happy to help you out.

However, release removals should not be requested trivially. The release removal is a somewhat time consuming manual procedure. If even a small number the maintainers of the thousands of libraries in the registry regularly submitted release removal requests, we would be forced to no longer offer the release removal service due to Arduino not having the resources to accommodate a large number of requests. We do not offer this service to allow library maintainers to get a "do over" when there is a flaw in a release.

I saw from your explanation in the related PR that the sole purpose for your request is a "do over":

#7499 (comment)

Making multiple releases with the same version number is a terrible development practice. In the case that there is a flaw in a release, the responsible thing to do is to simply fix whatever was wrong in the problematic release, bump the version number in the version field of the library's library.properties metadata file, then make a new release or tag in the library repository.

Making a new release will be superior for you and for the library users for the following reasons:

• The new release will be published in a matter of hours by the automated Library Manager system. Conversely, it may take days or weeks for us to find time for the manual work required to accommodate a removal request.
• Users who already installed the bad release will get an update offer for the new release. Conversely, if you re-release then anyone who already installed the bad release will not get an update.
• Users would find it confusing for there to have been two releases with the same version number, but technical differences.

[TanishKunthe]

Hi Per, I understand the policy regarding release removal requests and the reasons for closing Issue #7503 as "not planned." Thank you for the detailed explanation and the clear guidance on the proper procedure for addressing flaws in a release by bumping the version number and creating a new release. I have noted this best practice and will proceed with the suggested approach. I apologize for the inconvenience and thank you for guiding me through this process. Best regards, Tanish Kunthe

…

On Wed, 31 Dec, 2025, 1:47 am Per Tillisch, ***@***.***> wrote: *per1234* left a comment (arduino/library-registry#7503) <#7503 (comment)> The release removal service is provided by Arduino for emergencies where some content that absolutely must not be published (e.g., a copyright violation) was accidentally included in a release. If such an emergency has occurred then we are happy to help you out. However, release removals should not be requested trivially. The release removal is a somewhat time consuming manual procedure. If even a small number the maintainers of the thousands of libraries in the registry regularly submitted release removal requests, we would be forced to no longer offer the release removal service due to Arduino not having the resources to accommodate a large number of requests. We do not offer this service to allow library maintainers to get a "do over" when there is a flaw in a release. I saw from your explanation in the related PR that the sole purpose for your request is a "do over": #7499 (comment) <#7499 (comment)> Making multiple releases with the same version number is a terrible development practice <https://git-scm.com/docs/git-tag#_on_re_tagging>. In the case that there is a flaw in a release, the responsible thing to do is to simply fix whatever was wrong in the problematic release, bump the version number in the version field of the library's library.properties metadata file <https://arduino.github.io/arduino-cli/latest/library-specification/#library-metadata>, then make a new release <https://docs.github.com/en/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository> or tag <https://git-scm.com/docs/git-tag> in the library repository. Making a new release will be superior for you and for the library users for the following reasons: - The new release will be published in a matter of hours by the automated Library Manager system. Conversely, it may take days or weeks for us to find time for the manual work required to accommodate a removal request. - Users who already installed the bad release will get an update offer for the new release. Conversely, if you re-release then anyone who already installed the bad release will not get an update. - Users would find it confusing for there to have been two releases with the same version number, but technical differences. — Reply to this email directly, view it on GitHub <#7503 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A3LNRTFFQYHVZOXQ7WOK4JT4ELMUPAVCNFSM6AAAAACQKBQ74KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMBQGQ2DCNBQGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>