Fails the build when .github/workflows/actions.lock stops matching the
workflows, or when a locked pin no longer verifies upstream, so a stale or
tampered lockfile cannot go unnoticed between dependency updates.
Mutable action tags are a supply-chain risk: a moved tag runs different code
without a diff. Every workflow action is now pinned through
.github/workflows/actions.lock, and CI verifies the lockfile so an out-of-sync
or tampered one fails instead of running.
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
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).
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
The Flatpak check took any entry with this app's X-Flatpak and a flatpak run
Exec as on, also one a startup manager had hidden (Hidden=true, or GNOME's
X-GNOME-Autostart-enabled=false) or whose Exec started a different app.
It now reads the [Desktop Entry] keys as desktop-entry parsers do and
counts the entry only when it isn't hidden and its Exec is exactly the line
this launcher writes for its own app id.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
After switching from the host build to the Flatpak, the old host entry has
the same file name, so the setting showed on while its Exec still named the
host program. In the Flatpak only the Flatpak form (X-Flatpak=<id> and an
Exec of flatpak run) counts as on, and turning it on rewrites an old entry.
Both manifests grant xdg-config/autostart:create. Flatpak resolves that
on the host and binds the folder at its own path (common/flatpak-context.c,
common/flatpak-exports.c), so the entry can be written there also when
$XDG_CONFIG_HOME is outside home, and the folder is made on a fresh account.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Recompute the current revision, options and download plan when report_download rejects stale work. Add a real publication-boundary regression that fails with a missing plan before the fix and checks the accepted size plus Paused/Ready events. Local validation: serial native suite 279 passed, 3 existing ignored; Windows MSI integration 1 passed; strict all-target Clippy and repository formatting passed. The first parallel suite hit two unchanged HTTP fixture failures; both pass in the complete serial run.
Move the existing plan report after detected-state publication so post-job invalidation does not erase it. Strengthen the real-worker JobFinished observer regression: it fails with a missing plan before the fix. Full native validation passes 278 unit tests (3 existing ignored), the Windows MSI integration test, strict all-target Clippy and scoped formatting.
Observe the background Configure result before exercising stale-report rejection. Keep the existing plan and installed-format assertions, while excluding unrelated apps from the no-stale-events check. Full native validation: 278 tests passed, 3 existing ignored, plus the Windows MSI integration test; strict all-target Clippy passed.
Inside the Flatpak the autostart entry went into the sandbox's own config
folder (~/.var/app/<id>/config/autostart), which the host session never
reads, and its Exec line named the in-sandbox /app/bin path. When
/.flatpak-info exists the entry now goes into the host's autostart folder
($HOST_XDG_CONFIG_HOME, else ~/.config), is named after the Flatpak app id,
and starts the app with `flatpak run --command=artcraft-launcher <id>
--hidden` plus X-Flatpak, as the XDG Background portal writes it. Outside a
Flatpak the path and the entry are unchanged. Both manifests note that the
entry relies on --filesystem=home.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Keep the two newly merged upstream UI fixtures compatible with the existing download-size fake. Initialize its empty cache without changing either installability assertion.