Skip to content

Complete desktop release gates, native verification and AUR recipes - #22

Merged
LIghtJUNction merged 6 commits into
mainfrom
feat/desktop-release-completion
Nov 20, 2026
Merged

LIghtJUNction merged 6 commits into
mainfrom
feat/desktop-release-completion

Conversation

@LIghtJUNction

@LIghtJUNction LIghtJUNction commented Oct 22, 2026 •

Copy link
Copy Markdown
Member

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

  • Preserve the signing prerequisites, package-byte verification reports, engineering/release separation and desktop AUR recipes from this PR.
  • Merge main 8d6342a8194261f49cfb2c92fcc451ab23a72f3e, retaining its Mobile Web and Nix channels.
  • Resolve both generator conflicts and regenerate the Markdown, SVG and website catalog from the current release/latest.json. Published catalog entries remain CLI 0.1.4 and Server 0.1.0.
  • Keep formal Windows signing/timestamp, macOS Developer ID/notarization and complete-package publication checks mandatory. Engineering artifacts cannot update public downloads or desktop binary AUR recipes.

Local validation

Source head: 3d3e2f346e86635b45b19c829143ce93a8a6a8c3.

The GitHub tree ecd44a456ff3341f33277df83f10281e11b4c4eb exactly matches the development-machine tree tested at local merge 754aed2918fd9914ed47a583bc37bdb6f474ee61.

Passed:

  • python3 tests/release.test.py
  • python3 tests/desktop-signing.test.py
  • python3 tests/aur.test.py with real makepkg and bsdtar available
  • python3 scripts/release.py docs --check
  • Python syntax, package/publish shell syntax, desktop Rust formatting and git diff --check

The 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.

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
LIghtJUNction marked this pull request as ready for review November 20, 2026 12:43
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 20, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
🔒 Security Review ✅ Completed 2026-11-20T12:50:12.679947Z d2a5ef9 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants