User-Report: Auto-Update schlug mit "Setup-Asset nicht gefunden" fehl, wenn der Update-Check
waehrend des Asset-Uploads eines neuen Releases feuerte. Ursache: release:gitea pushte Tag +
erstellte das Release (draft:false) VOR dem Asset-Upload → das "latest"-Release war den ganzen
Upload ueber sichtbar, aber ohne latest.yml (Gitea-Assets haben keinen digest → der Updater
holt den Integritaets-Hash aus latest.yml, das zuletzt hochgeladen wird). Fix: Release als
draft:true anlegen → alle Assets hochladen → dann PATCH draft:false. Der Updater ueberspringt
Drafts und sieht das Release erst, wenn es komplett ist.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Fix ~70 issues across the entire codebase including security fixes,
error handling improvements, test stabilization, and code quality.
- Fix TLS race condition with reference-counted acquire/release
- Bind debug server to 127.0.0.1 instead of 0.0.0.0
- Add overall timeout to MegaWebFallback
- Stream update installer to disk instead of RAM buffering
- Add path traversal protection in JVM extractor
- Cache DdownloadClient with credential-based invalidation
- Add .catch() to all fire-and-forget IPC calls
- Wrap app startup, clipboard, session-log in try/catch
- Add timeouts to container.ts fetch calls
- Fix variable shadowing, tsconfig path, line endings
- Stabilize tests with proper cleanup and timing tolerance
- Fix installer privileges, scripts, and afterPack null checks
- Delete obsolete _upload_release.mjs
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
