changelog/v<major>/<major>.<minor>.x/<version>.md for each of the 42 releases from v1.0.0 to v4.7.1, and changelog/beta/ for pre-releases (none has been published; its README says how one would be filed). CHANGELOG.md becomes the index: what the layout is, [Unreleased] exactly as it was, and a table per major version (version, date, edition) that links each file. Each file is its section, copied byte for byte except that its heading is the file's H1 (so the sub-headings move up one level, outside code fences), relative links gain ../../../ so they name the same repository paths, and the --- separators between sections are gone. Checked by reversing all three changes on every file and comparing with the original section: 40 of 40 equal. Two releases had no section: v1.0.0 (its GitHub release notes, which the changelog pointed to as "Initial stable") and v1.1.3 (its tag message). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
3.0 KiB
v4.0.2 – 2026-09-29 (The "Right Address" Edition)
A game's tags, languages and store details are now re-read on a rotation
instead of being fetched once and never again, a long data job no longer loses
its work when something else lands on main, and each kind of message now has
an address of its own. Web app + desktop/Android bumped 2.0.1 → 2.0.2; repo
public-facing version 4.0.1 → 4.0.2.
The web changes are live as soon as this merges. The desktop app offers 2.0.2 through its updater once the release is published; on Android, install the new APK over the old one. Returning visitors see the consent gate once, listing the Privacy Policy, the Terms of Use and the Data Licence — each changed only by a contact address, and the gate shows exactly that line.
✨ Added
- Tags, languages and the rest of a game's store data now stay current.
update_data.pyonly fills in incomplete records, and only empty fields, so once a game had its tags, languages, platforms or header image nothing looked at them again short of a manual full re-fetch.Refresh Store Data(daily, 16:00 UTC) re-reads them on a rotation: the store page - tags, languages and their details, the paid-DLC flag - for every game once a week, and appdetails - name, header image, description, developer and publisher, release date, platforms, Metacritic, DRM notes - once a month. About 630 store pages and 150 appdetails calls a day instead of 8,800 requests in one sitting. It never blanks a value on a failed or age-gated page, never touches the hand-set fields (genre, type, anti-cheat, safety, notes), and marks a game updated only when something changed. A dry run on three games found all three with tags that had drifted since they were first fetched.
🐛 Fixed
- A long data job lost its work if anything landed on
mainmeanwhile.purge-unhealthyran for four hours on 2026-09-21 and then failed onpush rejected (fetch first): the data-write group serialises workflows, but a merged pull request or an/admincommit still movesmain. Every data job now commits throughbash/commit_push.sh, which rebases ontoorigin/mainand retries the push.
📇 Contact
contact@poli0981.dev stays the default. Three role addresses join it, each
published where a reader of that document would look:
| Address | For | Where |
|---|---|---|
security@poli0981.dev |
vulnerabilities, after GitHub's private reporting | SECURITY.md, /.well-known/security.txt |
privacy@poli0981.dev |
privacy questions | Privacy Policy |
copyright@poli0981.dev |
copyright, DMCA and takedown notices | Data Licence, Terms of Use §6 |
The maintainer's website, https://poli0981.dev/, is on the About page next
to the email and the links page. security.txt now lists GitHub's private
vulnerability reporting first and security@ second, in RFC 9116 preference
order. The full map is in AUTHORS.md and docs/Contact.md.