Release validation#
Sysand Index validates published releases so readers can see whether a package loads cleanly with the Sysand and Syside tools used by the index. Validation is shown on project pages as a badge and on each release’s validation page as a more detailed diagnostic report.
Release validation is separate from upload validation. Upload validation checks
whether a .kpar archive is acceptable before Sysand Index stores a release.
Release validation runs after a release has been accepted and records what
happened when the index tried to load the published package.
For the exact upload-time archive requirements, see KPAR archive validation. For exact release-validation states, stored fields, and queue behavior, see Release validation.
What release validation checks#
A validation attempt is a load check: Sysand Index sets up the published package in a fresh workspace, resolves its dependencies, and asks Syside to load its sources, much like a new user installing the package for the first time. For the exact steps of each attempt, see Release validation.
The validation report can include parser, validation, and semantic diagnostics from Syside. The report also records the Sysand and Syside versions used for the latest attempt when those versions are available.
What validation does not mean#
Validation is a machine check of how the package loads with the current index tooling. It is not a review of the package’s engineering quality, license compatibility, security, or suitability for a particular project.
A validated release can still contain modeling mistakes that the tools do not detect. A release with warnings or errors can still remain published because published versions are immutable: fixing a release means publishing a new version.
When validation finds a problem#
Open the release’s validation page and read the diagnostic table. The location
column points to the file and position when the tool reported one. Fix the
source project, rebuild the .kpar archive, and publish a new version.
For a first publish workflow, see Publishing your first project.