Houmeres/SageTube
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity
Files
2420091a4e8ded6eeec1899539d9a91968790b06
SageTube/CHANGELOG.md
T
Homer 2420091a4e Check for SageTube updates, not YTSage's 
The update check asked PyPI for the `ytsage` package's version, asked GitHub
for oop7/YTSage's release notes, and pointed the download button at upstream's
releases. None of that describes this program. Being reminded to install
YTSage was the visible symptom; the cause was that the check had never been
repointed when the fork was made.

It now reads SageTube's own releases from git.houmeres.sk. Gitea's release API
is shaped like GitHub's, so the dialog and the caller are unchanged -- the
class keeps its name and signal signature, and only its body moved out to
core/ytsage_app_update.py, which is fork-owned and will not conflict on the
next merge from upstream.

Upstream's inherited tags end in `b` (v5.3.0b and earlier). packaging reads
that as a beta marker, so they sort below v5.4.0 and a stable instance cannot
be handed one. Tag parsing is defensive anyway: one unparseable tag must not
take the whole check down with it.

Also: the check is rate-limited to once a day rather than every start, the
dialog gained a "Skip this version" that survives a restart, the thread is now
joined on close, and the About dialog says SageTube. The three binary updaters
-- yt-dlp, Deno, ffmpeg -- legitimately track their own upstreams and are
deliberately untouched; ytsage_app_update's docstring says so, because "update"
is an overloaded word in this codebase.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-09 00:36:14 +02:00

3.2 KiB
Raw Blame History

Changelog

Kept as the work happens, not assembled at release time. Format is Keep a Changelog; versions follow SemVer.

The vX.Y.Z tags already on this repository are upstream YTSage's, inherited with its history. SageTube's own versions start below and are the ones this file records.

Unreleased

Changed

  • The update check now looks at SageTube's own releases. It queried PyPI's ytsage package for the version and oop7/YTSage for the changelog, then linked to upstream's downloads — a different program's release stream. It now reads git.houmeres.sk/Houmeres/SageTube releases, anonymously, and the "Download update" button opens this repository's release page.
  • The beta channel follows SageTube pre-releases. Upstream's inherited b tags (v5.3.0b and earlier) read as pre-releases, so a stable instance cannot be offered one.
  • The check now runs at most once a day rather than on every start.
  • The About dialog and the update settings say SageTube rather than YTSage. The "Based on YTSage by oop7" attribution link stays — it is the MIT credit.

Added

  • Skip this version in the update dialog. The skipped version is never offered again; later ones still are.

Fixed

  • The app no longer offers upstream YTSage's releases as its own updates. __version__ and pyproject.toml had been left at the scaffolded 0.1.0 while the released tag was v5.4.0, so every comparison against upstream's published version reported an update. Both now read 5.4.0, the single source of truth for the window title, the About dialog and the update check.
  • ConfigManager merged a stored config over the defaults shallowly, so a file written by an older build replaced whole nested objects: a stored "player" or "feed" containing only some keys silently discarded every default added since. The merge is now recursive. Keys present only in the stored file are preserved, so downgrading cannot destroy settings.
  • Opening Custom Options and clicking OK re-enabled the update checker, because the settings tab read a missing check_app_updates as enabled and then persisted that reading unconditionally.

Changed

  • Configs now carry config_version. A file written before 5.4.0 — including one inherited from an upstream YTSage install — has its stored check_app_updates cleared once, so SageTube's own default applies rather than a setting that pointed at another project's releases.

5.4.0 — 2026-08-08

Changed

  • The documentation left the repository: docs/BUILDING.md, docs/UPSTREAM.md and docs/UPSTREAM_README.md are now the wiki.
  • The history was deliberately not rewritten. Every other repository in this org had its documentation removed from every commit on 2026-08-08. SageTube is a fork that still merges from oop7/YTSage, and a rewrite changes every commit id — which would end that. The files leave in an ordinary commit instead.
  • .github/ and readme-translations/ are upstream's and were left alone, so the next merge does not conflict over them.
Reference in New Issue View Git Blame Copy Permalink