fix: Repair release installer workflow (stale/failing CI build) - #13
Open
coding-jona wants to merge 2 commits into
Open
fix: Repair release installer workflow (stale/failing CI build)#13coding-jona wants to merge 2 commits into
coding-jona wants to merge 2 commits into
Conversation
…fixed installer Root cause of the 'Tarno Mesh crash' recurring for the user after PR #11: that fix landed in src/ (main), but the only published installer (Tarno Mesh v1.2.0 Beta, released 2026-08-14T21:11) predates the fix (merged 2026-08-15T07:54) - the user was reinstalling a stale build. Worse, the release_installer.yml workflow that would produce a new installer was itself broken and has been failing since before that release: it calls a module/script layout that doesn't exist in this repo (workspace/debug/installer/pipeline/build_all, .../scripts/sign_installer.py, .../scripts/checksums.py, .../tests) - leftover from a build approach that was superseded when the real build files were consolidated into workspace/installer/ (build.ps1, 'Tarno Mesh.spec', setup.iss, build_installer.py). Its one recorded run (31841362533) failed at the test step and never reached the (nonexistent) build step, so no working release has ever been produced by CI. Rewrote the workflow to mirror the actual local build process (workspace/installer/build.ps1): dotnet publish the WinUI 3 frontend, PyInstaller-bundle the backend with 'Tarno Mesh.spec', install Inno Setup via choco, compile setup.iss, checksum and upload the real installer artifact from workspace/installer/Output/. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
PyInstaller refuses to run with the obsolete enum34 backport present (it shadows the stdlib enum module on Python 3) - a transitive dependency pulls it into the fresh CI venv. workspace/installer/build_installer.py already works around this locally via cleanup_obsolete_packages(); mirrored here. Found via a live workflow_dispatch run of the rewritten workflow (run 32139672864), which failed at exactly this step. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Der gemeldete Tarno-Mesh-Absturz (startet, beendet sich sofort) ist bereits in main gefixt (PR #11, gemerged 2026-08-15T07:54). Aber:
release_installer.yml, der Workflow der einen neuen Installer bauen würde, war selbst seit vor diesem Release kaputt: er ruftworkspace/debug/installer/pipeline/build_all,.../scripts/sign_installer.py,.../scripts/checksums.pyund.../testsauf - Pfade, die es in diesem Repo nicht (mehr) gibt (Überbleibsel eines überholten Build-Ansatzes, seit der echte Build inworkspace/installer/konsolidiert wurde). Der einzige aufgezeichnete Lauf ist fehlgeschlagen, bevor er überhaupt den (nicht existierenden) Build-Schritt erreicht hat.Fix
release_installer.ymlneu geschrieben, um den tatsächlichen lokalen Build-Prozess (workspace/installer/build.ps1) nachzubilden:dotnet publishfür das WinUI-3-FrontendTarno Mesh.specsetup.issworkspace/installer/Output/Verifikation
CI (Tests) muss grün laufen; zusätzlich manuell per
workflow_dispatchausgelöst, um zu bestätigen, dass tatsächlich ein Installer entsteht.🤖 Generated with Claude Code