v0.9.3
19 October 2026
The license is now AGPL-3.0-only with a site exception, and data:migrate moves a site to the current data/ layout.
Added
phlat data:migrate [--apply]movesdata/from the old layout, wherestorage/held everything, to the current one. The deploy key moves fromstorage/gittogit/, with a.gitignoreof its own.storage/cache,storage/filesandstorage/addons/clockworkare deleted, since the site makes them again incache/./cacheand/gitare added todata/.gitignore. It is a dry run until--apply.phlat health:checkwarns while the oldstorage/folders exist, and points todata:migrate.task phlat:release:publishcreates the Forgejo release for the tag atHEAD, with notes from itsupdates/post, or the commit log when there is none. It needsFORGEJO_TOKEN.TAG=picks another tag, andUPDATE=1rewrites the notes of a release that exists.task phlat:labels:synccreates or updates the Forgejo labels from.forgejo/labels.json.
Changed
- The license is AGPL-3.0-only, replacing GPL-3.0. An additional permission (
LICENSE-EXCEPTION) leaves the contents ofsite/,data/and any addon outsidephlat/out of the covered work, as long as they contain no part ofphlat/.composer.jsonandpackage.jsonsayAGPL-3.0-only. .forgejo/is left out of release archives.
Fixed
DeployKey::generate()always writes a.gitignorecontaining*beside the History deploy key, so the key is never committed, whatever the project's own ignore rules say.
Comments
No comments yet. Be the first!
Loading form…