mirror of
https://github.com/screentinker/screentinker.git
synced 2026-08-13 22:03:13 -06:00
3b23600d97
The changelog stopped at 1.9.2-patch2, so 23 shipped releases had no entry — including the whole transition engine, group sync, the device-owner foundation, the hardening pass and every #234 fix. Anyone deciding whether to upgrade, or working out which release changed a behaviour, had nothing to read between 1.9.2 and now. Written from the actual commit ranges between tags rather than from memory, and pitched at the question a reader has ("do I need this, and what will change") rather than as a commit dump. Detail scales with the release: 1.9.5 (group sync, device-owner foundation, agency folders) and 1.9.25 get real explanation; 1.9.9 and 1.9.19 get two lines, because that is what they were. The 1.9.16 hardening entry describes each fix in the same neutral terms as its commit — the invariant restored, not the weakness. This is a public repository, some findings from that review are still open, and exploitation detail helps nobody deciding whether to upgrade. The advice there is just "upgrade". Also adds a CHANGELOG check to bump-version.sh: it warns if the release being cut has no entry. Deliberately a warning and not generation — a generated changelog is worse than none, since it reads like documentation while saying nothing. This only stops a release being cut silently without one, which is how the file fell 23 versions behind. |
||
|---|---|---|
| .. | ||
| backup.sh | ||
| bump-version.sh | ||
| debian-13-setup.sh | ||
| finalize-release.sh | ||
| find-orphan-zone-items.js | ||
| indexnow-submit.sh | ||
| install-service.sh | ||
| migrate-multitenancy.js | ||
| mint-billing-token.js | ||
| parity-multitenancy.js | ||
| raspberry-pi-setup.sh | ||
| remotedisplay.service | ||
| reset-admin.js | ||
| upgrade.sh | ||
| windows-setup.bat | ||