Files
inkwell/desktop/packaging
bvandeusenandClaude Opus 5.5 f2b48069e3
CI & Build / Build now, or wait for Android? (push) Successful in 2s
Desktop (Tauri) / Build, or is the channel already serving this? (push) Successful in 3s
CI & Build / Web typecheck and unit tests (push) Successful in 10s
CI & Build / Python lint (push) Successful in 1s
Android / Build, or is the channel already serving this? (push) Successful in 3s
Android / Core and FFI clippy and tests (push) Skipped
Android / Kotlin + Rust (APK) (push) Skipped
Android / Build the server image (push) Skipped
CI & Build / Python tests (push) Successful in 13s
Desktop (Tauri) / Web tests, clippy, Rust tests and rustfmt (push) Successful in 1m45s
Desktop (Tauri) / Windows installer (cross-compiled) (push) Successful in 1m56s
Desktop (Tauri) / Update manifest (push) Successful in 4s
CI & Build / integration (push) Successful in 1m31s
CI & Build / Build & push image (push) Successful in 14s
Desktop (Tauri) / Tauri desktop (Linux) (push) Successful in 2m59s
The AppImage tree is readable by everyone before it is repackaged
appimagetool's continuous build from 2026-10-29 rejects a tree that not every
user can read and run, which failed the desktop Linux lane. Extraction keeps the
build's restrictive modes (0700 directories, a 0770 AppRun.wrapped), and an
AppImage runs as whichever user launches it, so the modes are corrected rather
than the check skipped.

Issue #6712.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-30 10:09:58 -04:00
..