You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @Gitshaoxiang. A release tag is expected to be an immutable marker at a specific point in the repository history. It is a bad idea to ever move a release tag:
The problem is that anyone who already installed 0.0.9 before the re-tag would have one version of the library code, while everyone who installed it after the re-tag will have a different version. That will create an incredibly confusing situation for the users and library maintainers.
What you should do instead is simply make a new release (e.g., 0.0.10) to distribute whatever changes you originally intended to distribute via the 0.0.9 release. The 0.0.9 release will still be available for installation via Library Manager, but that isn't a problem because Library Manager always offers the latest release by default so the users will install 0.0.10.
If there is something in the 0.0.9 release that absolutely must not be distributed, then you can permanently delete that tag from the repository and then submit another release removal request. But please note this sort of request should only be made under exceptional circumstances because it requires a manual process for us to accommodate such requests and if there is widespread unnecessary submissions of such requests by the maintainers of the >5000 libraries in Library Manager, we would be forced to change our policies to no longer allow release removal requests.
Library name
M5Family
Version to remove
0.0.9
The text was updated successfully, but these errors were encountered: