release: v1.33.0

[geodro]

The stable that closes the 1.32.0 line.

The second design law says no feature may know the name Laravel, and most of this release is what happened when a real Drupal site was linked and every surface was asked about it in turn. The databases card read DB_HOST and DB_DATABASE out of a .env that a Drupal or WordPress project does not have, so neither was ever shown as owning the database it runs on. The doctor reported an empty database and offered migrations against a 0-byte file the application never opens, took its migrate button from the literal word Laravel spells that command with so Symfony and Drupal got a finding naming a remedy the user then had to go and find, and called a site healthy while it picked mysql in .lerd.yaml and served every request off SQLite. lerd env reported success and appended constants to a settings.php sitting next to the $databases array Drupal actually reads. mail() could not deliver anywhere in any container while Mailpit ran the whole time. These were never separate bugs so much as one assumption made in a dozen places, and each of them is answered from the framework's own declaration now: which file, in which format, at which keys, with which command. Writing one is the harder half, since a settings file is mostly guidance a user may have edited, so only the statements whose values change are rewritten and a read-only file is unhardened for the write and restored after.

The dashboard stopped being somewhere you watch lerd and became somewhere work starts. The + in Sites was a directory browser that streamed a link and stopped there, so a site linked from the dashboard took the defaults for PHP version, HTTPS and services with the user finding out later, and nothing ran the setup steps, which is where composer install, the JS build and the workers actually happen. It is a wizard now that either creates a project from the catalogue the store publishes or links one that exists, asks the questions lerd init asks, and runs the setup steps with their output streaming into the modal. Those questions and that step list are not a copy of the terminal's, they are the same plan, which is what lerd setup --list-steps and --step exist for. Everything reaching the host goes through one run endpoint that builds every argv itself from a named kind, and a run lives in lerd-ui rather than in the request that started it, so the modal can be closed mid-composer and picked back up. The documentation moved to the copy already embedded in the binary, searchable and rendered offline, which is the one moment a developer most needs it.

More of what lerd does is a line of YAML than it was a release ago: how long an engine gets to shut down, which of its complaints are structural noise on a restore, the command that clears a framework's cache, the one that runs its migrations, whether a setup step belongs only on a project nobody has bootstrapped yet, and the mark and colour it wears. That is only safe because a definition reaches every install within a day whatever binary it runs, with no version gate in the index or the schema, and this cycle is when that stopped being a hope. Writing an env format a binary had never heard of used to fall through to the dotenv writer, which appends key=value lines into a PHP file and takes the site down with a parse error on a machine whose owner did nothing but leave lerd running. It refuses now, says so, and leaves the project exactly as it was, and every key added to either schema since is either ignorable by an older binary or paired with one that is.

The long tail is mostly things that had been wrong for a while. A Homebrew upgrade retired the keg every service unit and every shim had recorded, so the whole install stopped at once on a machine where the developer changed nothing, behind a guard written for exactly that which could never fire on Linux because the executable path is already resolved there. Deleting a project directory left its certificates, its per-site container, its worktree vhosts and its open shares behind, and removing a site's certificates turned out to be dead code on every path including unlink. phpMyAdmin opened on whichever engine happened to sort first rather than the one its preset declares, so a user's mysql databases looked like they had vanished, and every POST it made came back as a connection error because the overlay put its session cookie in third-party territory. service remove --purge renamed the data dir aside and called that recoverable when only the image that wrote it could ever open it again. And the resources widget reported lerd-ui holding almost two gigabytes while the process held fifty megabytes, measured by a podman stats stream whose entire cost was charged to the process doing the measuring.

What is listed under Fixed is what a 1.32.0 install actually runs into. Two reviews of everything merged since the release sit behind this one, and what they found in this cycle's own new work is described inside the feature it belongs to rather than listed as a fix, since no released version ever had it.

The README picks up the env contract, the dashboard wizard, the offline docs, the nine frameworks the store publishes with their marks, the doctor's new fixes and the pre-wipe snapshot. The MCP reference gains the same env contract, sqlite as a wiring rather than a service, and the three doctor fixes that run on the host rather than in the container. The demo was answering every mark endpoint with an empty object, so the landing page showed none of the artwork this release is largely about; it carries the store's marks now and the social preview is recaptured from it, with a 2200x1100 featured variant alongside. The dev digest and its card are new with the banner pointing at them.

Refs #1432