Library release removal request

[belem2050]

Library name

LightTaskScheduler

Version to remove

1.0.0

[per1234]

Hi @belem2050. We do accommodate release removals in cases of emergencies where it is essential that some data must not be available via Library Manager. However, I am skeptical about your request.

You are making this request only minutes after submitting your library (#6242), and only minutes before attempting a redundant submission (#6244). This makes me suspect that you are hoping to accomplish something other than the removal of a release that contains illegal or dangerous data. If so, there is a correct way to accomplish your goal, and it is likely that the release removal you are requesting here would not even be effective if it was permitted.

So please provide a detailed explanation of exactly what it is you are trying to accomplish in a comment here. That will allow me to advise you on the correct way to achieve it.

[belem2050]

Hi @belem2050. We do accommodate release removals in cases of emergencies where it is essential that some data must not be available via Library Manager. However, I am skeptical about your request.

You are making this request only minutes after submitting your library (#6242), and only minutes before attempting a redundant submission (#6244). This makes me suspect that you are hoping to accomplish something other than the removal of a release that contains illegal or dangerous data. If so, there is a correct way to accomplish your goal, and it is likely that the release removal you are requesting here would not even be effective if it was permitted.

So please provide a detailed explanation of exactly what it is you are trying to accomplish in a comment here. That will allow me to advise you on the correct way to achieve it.

@per1234 Yeah, you're correct!
As I was explaining here, There was a typo that came into equation while committing, which is making the code not compiling

[per1234]

There was a typo that came into equation while committing, which is making the code not compiling

In the case where there is a bug in a release, the appropriate action is to fix the bug, increment the version, and then make a new release.

It sounds like you were planning to remove the bugged 1.0.0 release and then make a new 1.0.0 release with the code changed to fix the bug. That is not a responsible approach to maintaining a published project because then you can end up with a situation where the users may have either of two distinct variants of the project, but with the same version number, depending on when they installed it. That would be very confusing to the users and also make it more challenging to support the users. We do not accommodate release removal requests that are made for this purpose.

When you take the responsible approach and publish the fix by making a subsequent release, then Library Manager will inform the users who already installed the bugged version that a new version is available, and allow them to easily update the installed library. That would not occur if you re-released the same version, since Library Manager would have no way of knowing that the user's installation is outdated.

[belem2050]

Thanks so much for this put! I followed your recommandations.