Originally created by @StefMa on GitHub (Oct 30, 2024).
I just noticed that in case the DocPackageInfo.version is not a semver core version (MAJOR.MINOR.PATCH), then the Module will not be displayed in the overview:
The page is just empty ☝️
However, the files are beeing created.
Going to URL.com/com.github (com.github is the DocPackageInfo.name), the pre-version is displayed correctly:
Right now I'm not sure if this is an bug (Module is not displayed) or intented behaviour that should be documented.
Originally created by @StefMa on GitHub (Oct 30, 2024).
I just noticed that in case the `DocPackageInfo.version` is **not a [semver core version](https://semver.org/)** (MAJOR.MINOR.PATCH), then the Module will not be displayed in the overview:

The page is just empty ☝️
However, the files are beeing created.
Going to `URL.com/com.github` (`com.github` is the `DocPackageInfo.name`), the pre-version is displayed correctly:

Right now I'm not sure if this is an bug (Module is not displayed) or intented behaviour that should be documented.
pkldoc omits pre-release packages from the index page. So, given the current logic, this is expected behavior.
@bioball commented on GitHub (Oct 31, 2024):
pkldoc omits pre-release packages from the index page. So, given the current logic, this is expected behavior.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @StefMa on GitHub (Oct 30, 2024).
I just noticed that in case the

DocPackageInfo.versionis not a semver core version (MAJOR.MINOR.PATCH), then the Module will not be displayed in the overview:The page is just empty ☝️
However, the files are beeing created.

Going to
URL.com/com.github(com.githubis theDocPackageInfo.name), the pre-version is displayed correctly:Right now I'm not sure if this is an bug (Module is not displayed) or intented behaviour that should be documented.
@bioball commented on GitHub (Oct 31, 2024):
pkldoc omits pre-release packages from the index page. So, given the current logic, this is expected behavior.