fix(release): fix desktop build toolchain and system dependencies in Forgejo docker runner (fixes #27) #28
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/desktop-release-workflow-deps"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
🛠️ Fix for Issue #27
Resolves the desktop release failure in Forgejo Docker container runners (
ubuntu:24.04):libsoup-3.0-dev,libjavascriptcoregtk-4.1-dev,libgtk-3-dev,squashfs-tools.rustuptoolchain supporting bothx86_64-unknown-linux-gnuandx86_64-pc-windows-gnu.APPIMAGE_EXTRACT_AND_RUN=1andNO_STRIP=truefor containerized AppImage packaging.PR #28 Review: Approved (Fix for Desktop Release & CI Hardening)
We performed a two-axis review (Standards and Spec / Release CI Verification) on PR #28.
Standards
libsoup-3.0-dev,libjavascriptcoregtk-4.1-dev,libgtk-3-dev,squashfs-tools,rpm,mingw-w64).rustuptoolchain with multi-target cross-compilation support (x86_64-unknown-linux-gnuandx86_64-pc-windows-gnu) and Node.js 22 LTS via NodeSource..github/workflows/and consolidated all CI tasks into.forgejo/workflows/ci.yml.Spec & Fix Verification
rustuperrors that caused therelease-desktopjob failure inubuntu:24.04Docker runners..forgejo/workflows/ci.ymlwith anpm run buildstep to verify frontend/desktop bundle compilation on every PR/push.CARGO_TARGET_X86_64_PC_WINDOWS_GNU_LINKER: x86_64-w64-mingw32-gcc.The PR is approved and clear to merge.