6 Commits

Include renames

Author	SHA1	Message	Date
foxyzandClaude Opus 5.5	51c1c5ab78	Restructure step R: the app is Starsync (dev.foxyz.starsync) ... - Linux app id dev.foxyz.starsync, binary starsync; Windows starsync.exe, company foxyz; server starsync-server; Dart package starsync; archives starsync-<ver>-*. - 1.2.x compatibility: watch_together and watch-together-server launchers (Linux) / copies (Windows) in the archive; the updater accepts both names and relaunches the new binary; update.sh/.bat use whichever server exists. - First start copies (never moves) the old support folder and this app's Hive boxes out of ~/Documents into <support>/hive; a marker makes it run once; AppDirs is a port; settings schema version with ordered migrations. - Launcher entry dev.foxyz.starsync.desktop; the old one removed. - Repository name and URLs unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-15 20:21:20 +03:00
foxyzandClaude Opus 5.5	50bcc2e1a2	CI: Windows build + release on yuuka-windows ... tool/package_windows.ps1 builds watch-together-<ver>-windows-x64.zip (same layout as the Linux tarball, libmpv bundled, update.bat and watch-together-server.exe). The release workflow gets a windows job; ci runs the updater tests on Windows. Publishing moves to tool/release_publish.dart (dart: only, no python/bash on Windows), which tolerates both jobs racing to create the release and replaces an asset on re-runs. release.sh writes both asset URLs into the manifest. Windows jobs check out with plain git (the host's cached actions/checkout clone was corrupt). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-07 22:27:38 +03:00
foxyzandClaude Opus 5.5	8845007cbf	CI: create build/ before compiling the server; drop artifact upload ... upload-artifact@v4 is unsupported on Gitea (GHES error) and failed the release job after a successful build; the release asset is the artifact. dart compile exe doesn't create the output directory. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-07 03:38:59 +03:00
foxyzandClaude Opus 5.5	75d8651f17	Release CI: libmpv/epoxy deps, stable Flutter, multipart asset upload ... The v0.1.0 release job failed: media_kit_video needs libmpv-dev and libepoxy-dev at build time. Build on stable (what's verified locally), work on root-only runner images, upload the asset as Gitea's multipart attachment, and reuse an existing release on re-runs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-07 03:15:35 +03:00
foxyz	32848aaf71	Simplify release DX: local manifest, optional hash, slimmer publish ... release.sh writes updates/manifest.json at release time (predictable asset URL) — no CI commit-back, no push-token problem, no detached checkout dance. release_publish.sh is create-release + upload only. Manifest sha256 now optional; updater skips verification with a note when absent (HTTPS + gzip CRC cover the realistic cases). Fixed the repo-URL sed keeping a .git suffix (caught by a worktree dry run). Updater tests: 8 (sha-less manifest flow added).	2026-09-13 03:03:48 +03:00
foxyz	b0d93758f9	CI release pipeline in .gitea, wishlist into backlog ... release.yml (tag v* or manual dispatch): beta Flutter per local convention, Linux build deps, package script tarball, artifact upload, then release_publish.sh creates the Forgejo release, uploads the asset, and commits updates/manifest.json back to main. Workflows moved .github -> .gitea to match the forge setup. Wishlist.md consumed into roadmap backlog: EOF stall + tiny buffer bugs prioritized, recovery controls, link conveniences, time UI, shortcuts, shaders, avatar serving.	2026-09-12 20:38:17 +03:00