release: v1.30.0#1097
Merged
Merged
Conversation
The 1.30.0 line goes stable. What a PHP version owns keeps shrinking: custom extensions and packages become one declared set applied to every image lerd builds, with a realised set read back off each build so an entry a version cannot carry is reported absent rather than falsely present, and php.ini follows with a shared scope that fills the gaps under each version's own file. The dashboard reaches down to the data, managing an engine's databases from its service page with snapshots, export and import on the back of a single store-declared introspect query. Doctor learns to repair what it safely can, notifications gain a native desktop sink and a bell that keeps them, logs render in colour and hand themselves to a terminal, and git worktrees resolve their own PHP version, image, pin and database from wherever a command is run. The changelog folds both betas into one 1.30.0 section, since a fix for something introduced inside this line never reached a stable user. The exception is the DNS sudoers grant, which gets an entry because the behaviour is new relative to 1.29 and the documentation already promises it. The version bumps to 1.30.0 and the README picks up the extension set, log colour, the notification bell, the host-proxy reload and test-run tagging, none of which it had. Documentation gaps found alongside the release: the Databases tab was never described on the web UI page, the uninstall docs never said the sudoers grant is removed with it, the database page still described the LAN case as a 403 rather than a hidden tab, and the notification page said nothing about what reaches the bell under the native sink. The v1.30.0 dev digest ships with the landing page banner pointing at it. Each digest now carries its own generated social card instead of all seven sharing one image, along with article dates and JSON-LD, and a small generator reads the tagline and description back out of each page so a card cannot drift from what it fronts. The sitemap reads the digest directory rather than a hand-maintained list, which had already gone stale and left v1.29.0 unindexed. Demo fixtures gain the databases the new tab reads, which the landing page demo would otherwise have shown empty.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Promotes the 1.30.0 line to stable. Everything from the two betas plus the fifty-three commits that landed after beta.2, most notably the offline and post-sleep DNS work, the worktree resolution round where a branch finally runs the PHP version, image and database its own vhost serves, and a pass over what the daemon costs while nobody is looking at it.
The changelog folds both betas into a single 1.30.0 section rather than keeping their headings. Fixes for bugs introduced inside this line are left out of it, since for anyone upgrading from 1.29.0 those bugs never existed, with one exception: the database endpoint hardening is listed because it is a security fix, and the entry says plainly that it arrived during the betas and was fixed before stable.
The version bumps to 1.30.0 and the README picks up five capabilities it never listed, the custom extension set, log colour and follow in terminal, the notification bell, the host-proxy reload button and test-run tagging.
A docs pass alongside the release closed four gaps: the Databases tab had no entry on the web UI page at all, the installation page sold the passwordless sudoers grant with no counterpart saying uninstall removes it, the database page still described a LAN client getting a 403 rather than not being offered the tab, and the notifications page said nothing about what reaches the bell under the native sink.
The v1.30.0 dev digest ships, with the landing page banner moved onto it. Every digest now carries its own generated social card rather than all seven sharing one image, plus article dates and JSON-LD that og:type article had always implied and never had. A small generator reads each page's tagline, date and description back out of the page itself, so a card cannot drift from what it fronts, and the template carries all of it forward. The sitemap now reads the digest directory instead of a hand-maintained list, which had already gone stale and left the v1.29.0 digest unindexed since it shipped.
Demo fixtures gain the databases the new tab reads, without which the landing page demo would have shown the release's flagship feature empty.