chore: remove unavailable Veilance Market registry entry - #93
Conversation
|
@starkience could you please review this removal? The repository is confirmed HTTP 404, both official registry checks pass, and this entry currently blocks valid registration #86 from appearing on the hackathon hub. |
|
Bumping this: the dead |
Portablelle/veilance-market answers 404. validate-registry.mjs checks every entry in the file rather than the ones a pull request touches, so one dead repository failed the whole registry and no registration could be applied - eighteen open, nothing landed since 17 August, four teams reporting the same wall on #86, #95, #97 and #98. Applied from #93 by @BlackAporia, which recorded the removal correctly in registry-removals.json so the retention check knows it was deliberate rather than a merge dropping somebody. The underlying flaw is separate and follows: a broken row that is already on main must not be able to reject a registration that has nothing to do with it. Co-authored-by: BlackAporia <116606427+BlackAporia@users.noreply.github.com>
|
Applied to main as This was the entry blocking every open registration, and the queue moved as soon as it landed. The validator has also been changed so a broken row already on main is reported rather than failing somebody else's registration - thank you for the diagnosis, it was right. |
2 participants
Removes the registry entry for
https://github.com/Portablelle/veilance-marketand records the removal reason inregistry-removals.json.GitHub's API returns HTTP 404 for the repository. The unavailable entry currently makes shared registry validation reject unrelated registrations, including #86.
Validated locally with:
node scripts/validate-registry.mjsHISTORY_REF=upstream/main node scripts/check-registry-retention.mjsBoth checks pass.