mirror of
https://github.com/Evil0ctal/Douyin_TikTok_Download_API.git
synced 2026-10-20 23:49:37 +08:00
Evil0ctal
b4f6ff5c15
Version goes from 5.0.0.dev0 to 5.0.0 in the four places that carry it. `system.check_updates` now defaults to on. It was off with the note "the user opts in rather than being opted in", which is the right instinct aimed at the wrong thing: the check is made by the operator's browser and never by the server, so it carries nothing about the deployment. What it opts you into is finding out you are out of date, and an instance that never learns that is the more common harm on a self-hosted tool. Air-gapped boxes turn it off. Added the notice that goes with it: after signing in, once per 24 hours per browser, a modal if a newer release exists. Never for the demo account — a visitor cannot upgrade anything, and telling them how the operator runs their box is a small leak for no benefit. The comparison moved to lib/version.ts and got fixed on the way. The old one was an equality check that treated *anything* different as newer, so an instance built from main at 5.1.0.dev0 was told to upgrade to the older 5.0.0. It now understands that a pre-release is behind the release of the same numbers, which is exactly the 5.0.0.dev0 → 5.0.0 case this release creates. Seven cases checked, including that one. Both READMEs get an Updating section: pull, migrate, up, and the fact that named volumes mean the identity pool and archive stay put. Also two files for publishing releases — a bilingual template and the 5.0.0 notes written against it. English first, breaking changes above the feature list, and every entry says what the reader should do. Not committed here: nothing is tagged or published yet.