update reports the format it looked for when a release has no file for
the copy. The new test calls it with an empty release for every kind of
copy and checks that the format matches the one installs_from looks for,
so a change to craft-update's choice of format fails the test.
Adds step-security/harden-runner (audit, pinned to v2.22.4 like
craft-common-actions) as the first step of each job that did not have it,
so every workflow in the org's public repos reports its egress to
StepSecurity. Audit, not block: block-mode allow lists come from each
job's observed traffic.
* Load and verify the signed website catalog with bundled fallback
* Preserve signed fixture bytes across platforms and fix web lint
* Document the opt-in live catalog integration check
The launcher's self-update downloads the release file of the format the
running copy was installed from, and stops when the release has none. A
copy run outside the macOS app bundle updates from a .tar.gz, and the
launcher's macOS releases (v0.17.0 to v0.19.0) ship only the .dmg. Such a
copy was still offered "Update and restart", which then failed.
self_update::installs_from looks for that file with craft-update's own
pick_asset, as the update does. The backend reports self-update as
available, and starts one, only when the release has the file; otherwise
the update dialog and banner offer the download. The doc comment on
Capabilities::self_update states the new condition.
Detection stores the bare app name when it cannot find an MSI app's exe. Open checked it
with exists(), which looks in the launcher's working folder (its install folder). With the
apps in a custom folder beside the launcher a folder of that name is there, so the name
reached spawn and failed with "program not found" instead of the reinstall message.
Refs #1008, storytold/wordcraft#4831
Add MailCraft (UCS-Care-Group/mailcraft) to the catalog as a community app by
UCS Care Group, with its icon, licences, details page and tagline in every
complete catalog. Downloads are checked against its SHA256SUMS.txt. Its macOS
builds are unsigned, so mac_team is None: the launcher opens an installed copy
there but installs nothing.
AGENTS.md lists its repo as an approved community app (approved 2026-11-08).
When the waiting side could not open the elevated session's process for 10 seconds, the
session could still be running, but the batch ended with an error and released the
installer queue, so the next job could start beside it and stop with error 1618.
The queue now stays taken until the session's process ends, or until the session has
written its results and removed its process id, up to 4 hours.
The batch session's elevated copy took a package's path and checksum from a manifest
in the launcher's downloads folder, which any process of the user can write. The UAC
prompt names the launcher's publisher, so a manifest written by such a process could
get any MSI installed under that prompt.
The elevated copy now checks each held package's Authenticode signature against its
own, as the self-update helper does, and reports no exit code without running Windows
Installer when they differ. The launcher's side sends a package from another publisher
to install by itself under its own prompt, as SolidCraft and ArtCraft Studio do now.
The elevated copy also resolves the package's path before holding it and refuses a
symbolic link, so the path it checks is the one it installs, and it writes its
process id only to a new file.
Two review findings on the one-prompt session:
- The results file is bound to its session by a random token, written as
the file's first line and carried in the held manifest; a leftover or
planted file in the downloads folder can no longer pass for a
session's report. The session's name is only taken once its results
and process-id files are free too.
- The waiting side falls back to one-by-one installs only when the
elevated session is shown to be over (its process waited out, or its
process id gone). A session that was launched but cannot be seen to
finish - a slow antivirus start-up, a process that will not open -
now reports an error per app instead of racing a second installer.
The Linux gate never compiles this test, and Windows clippy stops at the
first hard error, so the field came to light only once the errors before
it were fixed.
Clippy on Windows (never compiled on the Linux gate) asked for two
things: run_msi now keeps to its caller's module, the visibility its
Package argument already has, and the session's cleanup-on-error uses
inspect_err, which is what removing a pid file on the way out is.
A job whose run_install ends before the installer is reached (a
repository-managed Flatpak, a missing release, the overwrite question, a
paused download) dropped its batch's gather without leaving it, so the
rest of the batch waited out the full ten-minute cap before their shared
prompt. The backend now holds the place with the same BatchPlace guard
install_at uses, so every way out of a job gives the place back.
* fix(macos): respect disabled Gatekeeper assessments
* fix(macos): read disabled assessment status on exit 1
* fix(native): allow the macOS-only exit details on other targets
Linux and Windows clippy (-D warnings) flagged RunOutput::code and the test
constructors as unused there. Same change as #1177.
Co-authored-by: AxoIsAxo <133877250+AxoIsAxo@users.noreply.github.com>
---------
Co-authored-by: AxoIsAxo <133877250+AxoIsAxo@users.noreply.github.com>
- Support ArtCraft Studio's published MSI and DMG asset formats in parse_asset_name while preserving existing asset naming
- Add real artcraft-release.json fixture and test asset selection across desktop platforms
- Add runs_on to CraftApp and filter out ArtCraft Studio on FreeBSD across backend and UI
- List ArtCraft Studio as app #01 in the README Craft App Suite table and xtask APPS array