Release news · 18 September 2026
PHP Ledger 1.0.0: the first stable release
1.0.0 consolidates the 0.6.1 workflow-recovery closure, the 0.7 browser installer and the 0.8 signed update/automatic-backup/recovery work into one supported stable release, published today from the interface introduced in 0.6.0-preview.
This is PHP Ledger's first stable release rather than another preview. It carries forward the warm light canvas, navy actions, local Inter fonts, workspace sidebar and company switcher from the 0.6.0-preview interface rebuild, and adds installation and update capabilities operators asked for.
What is new in 1.0.0?
- Workflow recovery. Save/post/reverse/source journeys preserve submitted values on a field error, with errors linked to their field, and report/source/action/return navigation is preserved through nested journeys.
- Browser installation. A new
/installentry sets up the application from a browser: host/database checks, the existing migration chain, private configuration, first-account creation and business onboarding, without Composer, Node or a terminal. - Signed automatic updates and recovery. An independent
/maintenance.phpoperator interface applies publisher-signed releases, taking an automatic matched code/configuration/key/database backup before applying a release and automatically restoring it if a migration or mutation fails.
What is the assurance status?
Before this release, automated test suites, fault-injection tests against the update/recovery path, exact-artifact installation/upgrade/recovery checks against a built package, and developer-operated browser checks of the installer and workflow journeys all passed. These are technical checks, not accounting or usability sign-off.
Independent accounting review, independent security review, supervised pilots including a real month-end close, installation observation by an unfamiliar operator, and recovery certification on a restricted shared-hosting account have not been performed. The owner is publishing 1.0.0 as the supported production scope with these limits disclosed, rather than waiting for those reviews; they continue as post-release commitments. Operators who need one of these assurances before deploying should arrange it independently before going live.
What remains unfinished?
Desktop and tablet are the design targets. Mobile refinement and dark mode are deferred. Complete visual and accessibility acceptance, consistent field-level validation recovery and the full nested report/source/action return journey remain unfinished. No WCAG certification, accounting sign-off, country compliance or restricted shared-host recovery certification is claimed. The updater currently requires a schema-owning database identity with DDL privileges and matching view/trigger definers; a separate low-privilege runtime identity with temporary update credentials is not implemented.
Try 1.0.0
- Choose a fictional business in the demo and review its Home and sample guide.
- Open Invoices, inspect a record and start a new draft. Review its lines, tax mode and posting preview.
- Open Profit & loss, choose a period and follow an account to its statement.
- Read the download page for the browser-installation and signed-update steps before considering real books.
Download and upgrade deliberately
The download page includes the application archive, checksum and matching release media kit. Compiled CSS and production dependencies are included; Node is not required on the server. The supplied migration chain is unchanged since 0.6.0-preview; 1.0.0 adds no new migration. Follow the packaged UPGRADE.md, stop writes and rehearse a matched code/database restore first, or use the signed in-browser updater once operator.key and the publisher's public key are provisioned.
These website screenshots are fresh 1.0.0 captures from a fictional media-kit demo business. They do not replace or change the published release archive or its media kit. See the versioned GitHub release for its verification record.