[codex] Treat Debian package validation as diagnostic - #277
Conversation
Greptile SummaryThis PR demotes the Debian 12 package-install gate from a blocking release step to a diagnostic baseline, reorders validation so Ubuntu 24.04 runs first (and is still blocking), and updates the documentation to stop presenting the broad-feature Ubuntu-family DEB as Debian baseline proof. The workflow logic is consistent: Confidence Score: 5/5This PR is safe to merge — workflow logic is correct, gating is preserved for the three mandatory distros, and documentation is consistent with the new posture. No bugs or logic errors found. The No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[validate-distro-install job] --> B[Fedora 42 — blocking]
B --> C[Rocky 10 — blocking]
C --> D[Ubuntu 24.04 — blocking]
D --> E[Debian 12 — continue-on-error: true]
E --> F[Upload distro validation logs — always]
D -->|fail| G[Job fails → release job blocked]
E -->|fail| H[Diagnostic failure recorded\nJob still succeeds]
H --> I[release job — needs validate-distro-install]
F --> I
I --> J[Upload signed assets to GitHub Release]
Reviews (1): Last reviewed commit: "Treat Debian package validation as diagn..." | Re-trigger Greptile |
Summary
Validation
.github/workflows/release-linux.ymland.github/workflows/test-distro.ymlTracker links
Notes
Release run
25087301829already proved the exact signed Fedora 42 RPM and Rocky 10 terminal-first RPM in KVM. Its remaining failure was the Debian 12 broad-feature DEB mismatch; Ubuntu was skipped only because Debian previously ran first and failed hard.