Repository navigation
Complete desktop release gates, native verification and AUR recipes - #22
Merged
Merged
Conversation
Re-enable scoped engineering builds for the existing platform matrix, add native smoke checks and signature evidence, preserve manual update semantics, and keep unreleased artifacts out of generated download catalogs.
Keep source and binary distribution separate, generate binary recipes only from published verified assets, and validate metadata and package boundaries with makepkg and bsdtar.
Handle the embedded license in noninteractive read-only DMG verification, retain native verification errors, and make the AUR source build self-contained with the matching Tauri custom-protocol feature and accurate Rust minimum.
LIghtJUNction
marked this pull request as ready for review
November 20, 2026 12:43
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Resolve the release generator conflicts by keeping the current Mobile Web and Nix channels together with the engineering/signing gates. Regenerate downloads from the current release/latest.json, preserving CLI 0.1.4 and Server 0.1.0. The tree exactly matches locally tested 754aed2918fd9914ed47a583bc37bdb6f474ee61. Release, signing-policy and real makepkg/bsdtar AUR suites, generated-doc checks, Python and shell syntax and desktop formatting passed. Native signed Windows/macOS/Flatpak release qualification remains a separate required gate; no tag, publication or deployment was performed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The desktop release branch overlapped newer download-catalog work on main. Merging the old generated files would have restored CLI 0.1.3 and removed the Mobile Web/Nix channel descriptions.
Changes
8d6342a8194261f49cfb2c92fcc451ab23a72f3e, retaining its Mobile Web and Nix channels.release/latest.json. Published catalog entries remain CLI 0.1.4 and Server 0.1.0.Local validation
Source head:
3d3e2f346e86635b45b19c829143ce93a8a6a8c3.The GitHub tree
ecd44a456ff3341f33277df83f10281e11b4c4ebexactly matches the development-machine tree tested at local merge754aed2918fd9914ed47a583bc37bdb6f474ee61.Passed:
python3 tests/release.test.pypython3 tests/desktop-signing.test.pypython3 tests/aur.test.pywith realmakepkgandbsdtaravailablepython3 scripts/release.py docs --checkgit diff --checkThe signing-policy tests use fixtures; they do not establish real Windows/macOS signing acceptance. The full six-platform and Flatpak build/signing qualification remains required before a formal desktop release.
Publication status
This is a source integration. No desktop tag, AUR upload, production deployment, signing identity, notarization credential or formal desktop release was created. Ordinary CI was not dispatched or retried during backlog cleanup. Existing formal release workflows and their gates remain in place.