v0.7.1
<p>Admin saves are recorded in History automatically, and the Changes page becomes a History page with one Sync button.</p>
6 October 2026
Added
- The admin records its own writes in History: a page saved, deleted or moved, an item saved or deleted, and a file stored, changed or deleted. The admin router calls
History::autoCommit()for its non-GET requests, so a GET never commits. Code that saves pages itself (the CLI, imports, a site's own routes) is not committed. History::sync()records anything still uncommitted underdata/pagesas one entry, fast-forwards from the remote, then pushes. It never merges: if the histories diverged it stops and says a developer must resolve it.History::refresh()fetches at most once a minute, with a timeout, soremoteStatus()can show what is waiting to send or receive.History::commitIfDirty(),commitMoved()andcommitOwner(), and thepage.delete:afterandpage.move:afterevents.Git::lastFetched().Git::fetch(),pull()andpush()take a timeout, andcommit()andcommitAll()return aGitResult.
Changed
- The admin Changes page is now History. It shows the remote's status with one Sync button, and the branch list when
features.versionsis on. The remote panel opens at once and fetches its status while it loads. - The admin's Publish action is renamed Save: saving turns the autosave draft into the page and records it.
- Restoring an old revision commits it as a new entry, so history is never rewritten.
- A failed commit is logged and the write still stands.
Removed
- The
git.commitsetting (manualorauto) and the Publish-as-commit step.History::mode(),maybeAutoCommit(),publish(),discardDraft(),changes(),diffPending(),revertField(),fetch(),pull()andpush()go with it, along with the Changes page's publish, discard, revert and diff actions and the separate fetch, pull and push buttons.
Comments
No comments yet. Be the first!
Loading form…