6 Commits

Include renames

Author	SHA1	Message	Date
seer	1052ac5fa5	Fix release workflow's manifest-commit checkout and correct 0.3.0.0 checksum ... The "Commit updated manifest to master" step left manifest.json dirty (modified during the tag checkout by package-release.sh) and then tried to git checkout master, which git correctly refused -- that's the CI failure from the v0.3.0.0 tag push. Discard the working-tree manifest.json before switching branches, matching the /tmp copy-then-restore pattern already used for carrying the update across. Also corrects the 0.3.0.0 manifest entry itself: it had been hand-edited locally with 0.2.0.0's leftover checksum instead of the real zip's hash, and had dropped the 0.2.0.0 history entry entirely instead of appending. Rebuilt via update_manifest.py against origin/master's manifest.json using the actual checksum of the already-uploaded v0.3.0.0 release asset.	2026-07-10 20:19:58 +02:00
seer	5015ffe2b4	FIx versioning	2026-07-10 14:13:17 +02:00
seer	7245bcf1ef	Revert "Split release publishing into a separate public distribution repo" ... This reverts commit 1d2246c5e2.	2026-07-09 17:23:11 +02:00
seerandClaude Sonnet 5	1d2246c5e2	Split release publishing into a separate public distribution repo ... Gitea has no per-release visibility override -- a repo is public or private for everything (raw files, releases, API), confirmed against Gitea's own docs/issue tracker. So manifest.json and release zips now publish to a dedicated public repo (JellyfinSyncPlus-repo) via Gitea's Contents API, while this source repo stays private. The v0.2.0.0 release already pushed under the old (source-repo-only) version of this pipeline is now stale; the next tag will publish correctly under the new split. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-09 17:21:04 +02:00
gitea-actions	6eb63449a9	Release 0.2.0.0	2026-07-09 15:11:21 +00:00
seerandClaude Sonnet 5	b83074d55f	Add SyncPlay stats-for-nerds page, manual sync button, and release pipeline ... Phase 0 scaffold plus everything since: quality negotiation, host-relay, and active drift correction were each built and reverted after real bugs in live use (see PLAN.md for the full account of each). What remains is read-only SyncPlay observability (live drift/playback stats page) and a one-shot manual "sync me to group" action, plus Phase 5 packaging/release tooling (build.yaml, manifest.json generator, Gitea Actions release workflow) to distribute it as a proper plugin repository. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-09 17:06:46 +02:00