Platform delivery matrix
Separate desktop installers from kernel artifacts before assessing coverage. A Linux kernel artifact is not a Linux desktop installer. A website download button is not proof of platform verification.
Desktop delivery matrix
| Target | Delivery and checks |
|---|---|
| macOS arm64 | Apple Silicon DMG; separately verify signing, notarization, staple, and launch. |
| macOS x64 | Separate Intel DMG; arm64 or Rosetta results cannot substitute for it. |
| Windows x64 | Full NSIS installer for offline installation and self-update; the online bootstrapper downloads and verifies that package. |
macOS also provides PKG downloads. PKG uses Developer ID Installer; DMG uses Developer ID Application. Verify them separately. The updater selects DMG: never put a PKG in its platform slot.
PKG certificate configuration errors block the signing lane. External PKG packaging or notarization failures after DMG completion follow the degradation rule. If either architecture lacks PKG, the download manifest falls back to both DMGs rather than offering a single-architecture PKG entry.
Kernel and desktop matrices differ
The kernel repository supplies platform bundles. Desktop embeds the version-bound sidecar. Check Linux GNU targets in kernel release records; do not count them as desktop installers or substitute npm and website builds for their results.
The bundle used by a coordinated desktop release must cover macOS arm64, macOS x64, and Windows x64. Each target needs evidence of version, provenance, digest, and runtime checks.
Package type changes the acceptance scope
Packages on the same operating system follow different delivery paths. Verify DMG and PKG signatures and installation separately. A Windows online bootstrapper also needs verification of the full installer it retrieves. Starting the bootstrapper alone does not validate download, integrity checking, and installation.
| Existing result | Supported conclusion | Remaining validation |
|---|---|---|
| arm64 DMG installs and starts | That architecture and DMG passed those checks | Intel and other package types |
| Both DMG architectures pass | Evidence covers both DMGs | PKG Installer signature and installation |
| Windows full installer passes | Full-package installation is verified | Bootstrapper retrieval and verification chain |
| Linux kernel bundle passes | Evidence covers that kernel target | No Linux Desktop availability claim follows |
Scenario: optional PKGs are incomplete
Separate required desktop coverage from optional packages. Both DMGs and Windows x64 form the required public-update set; PKG download entries require both architectures. One architecture's PKG is not a complete public PKG offering.
Handle signing-configuration errors separately from external PKG packaging or notarization failures after DMG completion, following release rules. Record the failed stage and actual fallback delivery scope. Providing DMGs must not be recorded as successful PKG verification. The matrix should explain which entry points can ship and which packages remain incomplete.
Record platform results
Record OS, architecture, installer URL, source SHA, digest, signature, platform checks, launch, and update exercises separately. Distinguish passed, failed, not performed, and out of scope.
Pre/Beta allow separate deliveries, but the public update pointer waits for all three desktop targets. Stable requires complete gates. See Verify and promote.
Fill out a delivery matrix
Use one row per version, operating system, architecture, and package type. Record kernel-bundle versions and digests separately. Each row needs a source commit, final download location, signature result, install/start result, update result, and evidence location. Mark unperformed platform tests as not run rather than borrowing another architecture's result.
The release owner first checks that all three required desktop targets are complete at the same version, then checks whether optional PKGs are available for both architectures. State whether each missing item blocks one artifact, the public update pointer, or Stable promotion. After repair, update only rows with new evidence and recheck version consistency across the set.