The Linux app now downloads the release archive to a temporary folder, verifies its checksum, extracts it beside the install folder, swaps the bundle in with two renames (keeping <install>.previous for rollback) and relaunches. A read-only install location is reported with how to fix it. The prompt and Settings button say "Install and restart".
Pipelines app
The Flutter client for Android, web and macOS.
macOS desktop
From app/, run:
FLUTTER=/Users/alan/development/flutter/bin/flutter python3 tool/publish_macos.py
This builds a release, installs it at ~/Applications/Pipelines.app, and opens
it. Run the same command to update and reopen it. The previous bundle is kept
at ~/Applications/Pipelines.app.previous; connections and settings stay in
the app's own storage. This does not restart the Pipelines server.
The default server comes from PIPELINES_SERVER_URL or the local installation
manifest. Override it with --server-url wss://host/connect. Existing saved
connections still take precedence over the build default.
Use --destination /path/to/Pipelines.app for another installation location,
or --no-open to install without launching (quit the app first). A ZIP is also
created at build/desktop/Pipelines-macos.zip. Use --offline when all
dependencies are already cached and network access is unavailable.
By default, the release and ZIP target this Mac's architecture (Apple Silicon or
Intel). --universal requests both; Xcode 27's lipo currently fails Flutter's
combined architecture check on this machine, so use the default here.
On macOS, Command+1…9 and Ctrl+1…9 open the corresponding conversation in the list and focus its composer.
Requires macOS, Xcode, CocoaPods and the Flutter SDK pinned in
.flutter-version. The local build is ad-hoc signed, without Apple notarization;
the ZIP is a local distribution artifact. Updates are applied by rerunning the
command; there is no background updater. Android's in-app update feed remains
Android-specific.