Leo Galambos
38620d7e71
Introduce contracted compiled patch tries for faster lookup, make compiled patch commands the primary runtime path, refresh stemmer benchmarks and documentation, and restructure the documentation for 3.0.0 onboarding. BREAKING CHANGE: Radixor 3.0.0 promotes compiled patch-command APIs and new compiled trie artifacts as the primary runtime integration model.
3.7 KiB
Reports and Published Build Artifacts
Radixor publishes durable build outputs to GitHub Pages from qualifying runs of .github/workflows/pages.yml.
This page is the central entry point for published project artifacts, including build summaries, API documentation, test and quality reports, benchmark outputs, and software composition materials. It is intended both for routine project inspection and for linking stable report surfaces from external references such as the README, release notes, or development workflows.
Stable entry points
The following links are the primary stable locations for the most recent published build outputs:
Use builds/latest/ when you want the current published report surface. Use builds/ when you need to inspect or compare retained historical runs.
API and developer documentation
These reports are primarily useful when reviewing the published API surface and generated developer-facing documentation:
Verification and code quality reports
These reports describe the outcome of core verification and static-analysis stages for the latest published build:
- Release verification test report (ciRelease)
- PMD report
- JaCoCo coverage report
- PIT mutation testing report
- Dependency vulnerability report
Together, these reports provide the most direct published view of functional correctness, static quality signals, coverage, mutation resistance, and dependency-level security review outputs.
Software composition artifacts
These artifacts expose the published software bill of materials for the latest build:
They are useful for dependency inspection, downstream integration, compliance-oriented workflows, and artifact traceability.
Benchmark outputs and badge metadata
These resources expose benchmark results and generated badge metadata derived from the latest published build. JMH benchmark reports are published as TXT and CSV files; the historical Porter comparison badge is no longer generated.
- JMH benchmark results (TXT)
- JMH benchmark results (CSV)
- Coverage badge metadata
- Mutation badge metadata
The benchmark outputs provide direct access to the published JMH result files. Coverage and mutation badge metadata endpoints are intended for status surfaces such as the project README or other generated dashboards.
Practical usage
In most cases, the recommended entry path is:
- start with the Latest build summary,
- open the specific report category relevant to your task,
- use Browse historical build reports when historical inspection is needed.