fix(flatpak): generate complete offline-buildable manifest for desktopApp (#5610)

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
James Rich
2026-05-26 13:33:23 -07:00
committed by GitHub
parent c55d6e0ac4
commit a4522f9f4d
8 changed files with 277 additions and 112 deletions

View File

@@ -374,11 +374,15 @@ jobs:
# network — meshtastic.flatpak-ops captures URLs via BuildOperationListener and
# only sees ExternalResourceReadBuildOperation events for cache misses. With the
# shared cache, downloads would be skipped and the manifest would be (nearly) empty.
# We drive packageUberJarForCurrentOS — the same task the in-flatpak build invokes —
# so the runtime classpath is fully resolved (skiko, ktor-cio, kable-btleplug-ffi, …
# are runtime-only and would be missed by :assemble).
- name: Generate Flatpak Sources
run: >
./gradlew --no-build-cache --no-configuration-cache
-Dgradle.user.home=${{ runner.temp }}/flatpak-gradle-home
:desktopApp:assemble :captureFlatpakSources
-I gradle/init-scripts/flatpak-ops.init.gradle.kts
:desktopApp:packageUberJarForCurrentOS :captureFlatpakSources
- name: Stage manifest
run: cp build/flatpak-ops-sources.json flatpak-sources.json

View File

@@ -576,11 +576,14 @@ jobs:
cache_read_only: true
# Isolated Gradle user home — see explanation in release.yml.
# packageUberJarForCurrentOS is what the in-flatpak build invokes; it resolves the FULL
# runtime classpath. :assemble alone would miss runtime-only deps (skiko, ktor-cio, …).
- name: Generate Flatpak Sources
run: >
./gradlew --no-build-cache --no-configuration-cache
-Dgradle.user.home=${{ runner.temp }}/flatpak-gradle-home
:desktopApp:assemble :captureFlatpakSources
-I gradle/init-scripts/flatpak-ops.init.gradle.kts
:desktopApp:packageUberJarForCurrentOS :captureFlatpakSources
- name: Stage manifest
run: cp build/flatpak-ops-sources.json flatpak-sources.json