Repository navigation
Closed
Labels
release-assurancePost-release assurance findingsPost-release assurance findings
Description
❌ Release assurance v0.28.0
13 of 16 checks passed; 3 failed and 0 reported nothing.
| Stage | Result | Checks | Passed | Failed | Missing |
|---|---|---|---|---|---|
| Release prerequisites | ✅ pass | 6 | 6 | 0 | 0 |
| Final pre-release checks | ❌ fail | 5 | 3 | 2 | 0 |
| Post-release assessment | ❌ fail | 5 | 4 | 1 | 0 |
Release prerequisites
| Check | Level | Result | Summary |
|---|---|---|---|
| Assurance catalog is valid | gate | ✅ pass | The assurance catalog is valid and every fixture and expected-result file it names exists. |
| Release binaries build for every target | gate | ✅ pass | All 12 release binaries built: full and lite for Linux, macOS, and Windows on amd64 and arm64. |
| Parsers survive malformed input | advisory | ✅ pass | 30 fuzz targets ran for 30s each against their seed corpus without finding a crash. |
| End-to-end scans of real projects | gate | ✅ pass | 22 instances passed. |
| Unit tests pass on every platform | gate | ✅ pass | 3 instances passed. |
| Java detector tests are stable | gate | ✅ pass | The Gradle, Maven, and sbt detector suites passed ten times in a row. |
Final pre-release checks
| Check | Level | Result | Summary |
|---|---|---|---|
| Every release file is attached | gate | ❌ fail | 22 of 23 expected release assets are attached. |
| Released binaries report this version | gate | ✅ pass | 3 instances passed. |
| Release files match their checksums | gate | ✅ pass | 3 instances passed. |
| Build provenance verifies | gate | ❌ fail | slsa-verifier could not verify the build provenance attached to this release. |
| Checksum list is signed | gate | ✅ pass | The checksum list carries a valid Sigstore signature issued to this repository's release workflow. |
Post-release assessment
| Check | Level | Result | Summary |
|---|---|---|---|
| Install scripts install the release | gate | ✅ pass | 3 instances passed. |
| Repeated scan speed and stability | advisory | ✅ pass | canonical-sbom-scan completed 5 samples per cache mode with identical normalized output (cold median 21 ms, warm median 21 ms). |
| Published files download and match | gate | ✅ pass | All 23 published files downloaded from their public URLs without credentials and match the signed checksum list. |
| The released binary scans real projects | gate | ✅ pass | 3 instances passed. |
| Official validators accept our SBOMs | gate | ❌ fail | SBOM interoperability run failed: validator java failed with exit 1. |
Needs attention
- ❌ Every release file is attached (gate, pre-release) — 22 of 23 expected release assets are attached. Logs: job.
- ❌ Build provenance verifies (gate, pre-release) — slsa-verifier could not verify the build provenance attached to this release. Logs: job.
- ❌ Official validators accept our SBOMs (gate, post-release) — SBOM interoperability run failed: validator java failed with exit 1. Logs: job.
Metadata
Metadata
Assignees
Labels
release-assurancePost-release assurance findingsPost-release assurance findings
Activity
bomly-guy commentedon Oct 4, 2026
Fixed in v0.28.1, whose assurance report passes every check. The three gates that failed here were release-assets and release-provenance (provenance was attached after the gate inspected the draft, fixed in #494) and sbom-interoperability (merged SPDX exports wrote SHA256 source-link checksums where SPDX 2.3 requires SHA1, fixed in bomly-sdk v0.14.7 and pinned in #495, which also moved the check before the tag).