Do not list packages without versions
What does this MR do?
Packages should be hidden from API results and human readable endpoints until at least one version could be fetched. This is not the case if versions are not fetched yet / an error occurred during fetching, and can cause problems with scripts that rely on there being at least one version.
Changes to public APIs
Author's checklist (required)
See https://gitlab.com/clean-nc/contributing#isocyanoclean-contributing-guidelines for the rationale behind these items:
-
The commit history does not contain merges (use git rebase -i main
if it does) -
Intermediate commits compile (use git rebase -i main
if not) -
Newly added code has a style consistent with the rest of the repository -
Newly added code is documented -
If bugs have been solved, tests have been added -
A changelog entry has been added if required