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
{{ message }}
Repository navigation
Exclude deleted and deprecated servers while validating remote urls. #1193
Closing with clarification of the existing lifecycle policy: deleted entries are already excluded from remote-URL conflicts; deprecated entries deliberately retain their URL reservation because they remain published, discoverable versions. A URL is released by deleting the versions that reserve it, not by deprecating them. The maintainer analysis in #1204 confirms the deleted-record behavior already exists, and that PR retains regression tests for deleted reuse, deprecated rejection and restore conflicts. Specific blocked migrations should remain tracked in their individual administrative requests.
Activity
rdimitrov commentedon Oct 23, 2026
Closing with clarification of the existing lifecycle policy: deleted entries are already excluded from remote-URL conflicts; deprecated entries deliberately retain their URL reservation because they remain published, discoverable versions. A URL is released by deleting the versions that reserve it, not by deprecating them. The maintainer analysis in #1204 confirms the deleted-record behavior already exists, and that PR retains regression tests for deleted reuse, deprecated rejection and restore conflicts. Specific blocked migrations should remain tracked in their individual administrative requests.