Dylan M. Taylor e5d3039747 fix: Flatpak review fixes, and add the signature lookaside for signed bundles ...

Review of #1147:
- A failed OCI migration precheck (no version in the remote's AppStream data, polkit refusing
  remote-add, offline) now falls back to the bundle update instead of failing it; only errors
  once the reinstall starts are reported. The ref must list exactly the selected version.
- `flatpak list` names a named installation `system (<name>)`; the parser keeps `<name>`, and
  one packages::flatpak_scope builds the --user/--system/--installation= argument everywhere.
- A repository-managed Flatpak on a pinned or nightly track gets the "update with flatpak"
  hint instead of a plain `flatpak update`, and status no longer offers a GitHub version for it.
- The migration refuses while the app runs; the origin check after the reinstall can't be
  cancelled; is_flatpark_origin matches only `flatpark`; settings_install keeps its doc; the
  no-op oci_migration Cargo features are gone.

Signed bundles (storytold/craft-common-actions#129): a signed bundle's origin has the release
key but no signature lookaside, which `flatpak build-bundle` can't record, so its first update
from the ArtCraft OCI repository fails with "no valid signatures". The updater then sets
--signature-lookaside=https://getartcraft.com/signatures on that origin once and retries;
any other origin or error is left alone.

2026-11-02 21:29:10 -05:00

..

src

fix: Flatpak review fixes, and add the signature lookaside for signed bundles

2026-11-02 21:29:10 -05:00

tests

fix: preserve Flatpak update scope and handle cancellation

2026-11-02 17:37:32 -05:00

Cargo.toml

fix: Flatpak review fixes, and add the signature lookaside for signed bundles

2026-11-02 21:29:10 -05:00