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
Swift-JSON: missing README and documentation link - metadata refresh request #4187
Please explain what data is incorrect and what you expected to see
Rechecked on 11 October 2026 at approximately 21:42 UTC:
The package's README panel says “This package does not have a README file.” The repository has a public root README.md; I expected it to appear in that panel.
There is no Documentation link. The maintainer information page reports “Has no documentation” and “Does not have a README file.” I expected Documentation to link to the live DocC site, which contains references for all four library products. The Package Homepage link already points to that same working site.
The repository now has this root .spi.yml, accepted by SPI's online manifest validator:
Could you please refresh/re-ingest the repository and README metadata and reanalyse the default branch so the external documentation link is picked up? If additional repository configuration is needed, I am happy to adjust it.
If the problem relates to the compatibility matrix, does it apply to specific builds?
This report concerns README and documentation metadata. I see the build backlog notice and understand that compatibility results may take longer; I am not requesting build priority or reporting an SPI build failure.
Additional context
This is a newly admitted package (PackageList PR #15642, merged today), so processing delay may explain the documentation update.
GitHub's README API returns the correct root file (16,508 bytes). A fresh request with Accept: application/vnd.github.html+json returns HTTP 200 and rendered README HTML with a #readme container and an article. I have not established why the metadata is missing on SPI.
Activity
finestructure commentedon Oct 12, 2026
Thanks for the report, @ThorFuchs
As to your first point, I see the REAMDE on the page:
Regarding the documentation link: this was added very recently and it will take a little longer for the package page to be updated.