v1.25.5

Changed

• Check now is a button. When you have already checked for updates today, "Check now" on the Installed tab is a real button instead of a text link, the same as within the week. An overdue check still gets the highlighted button. Suggested by ClaudiusH.

Updating

composer update ernestdefoe/millwright

v1.25.4

Fixed

• Extensions with no tagged release no longer say "could not check". Packagist keeps a package's branches in a separate file, and Millwright only read the file of tagged releases. Extensions that have never been tagged, such as fof/translate and fof/extension-releases, now show whether they work with your Flarum, judged on their branches (for example 2.x-dev).
• Install is only offered when your stability setting allows it. If the only release that works is less finished than Sources → How finished a release has to be allows, the card says "needs Dev in Sources" (or Beta, RC, and so on) instead of offering an Install that Composer would refuse with "could not be found in any version".

Reported by ClaudiusH.

Updating

composer update ernestdefoe/millwright

v1.25.3

Fixed

• Rebuilt with flarum-webpack-config 3.1.0, TypeScript 5.9, Prettier 3.9.10 and webpack-cli 7, the tooling Flarum announced in this post. Its lazily loaded parts now have a chunk store of their own, so they can no longer clash with another extension's and break the page.

Updating

composer update ernestdefoe/millwright
php flarum cache:clear

v1.25.2 — Learn more opens the release notes

Fixed

• "Learn more" opens the release notes again. The release notes window loads only when needed, from a separate file that Flarum was never told to publish, so the button failed with a 404 on every forum. Thanks to ClaudiusH.

composer update ernestdefoe/millwright
php flarum cache:clear

v1.25.1 — self-updates from the command line finish

Fixed

• Updating Millwright itself from the command line no longer stops at "Finishing up". The update replaced Millwright's files while the old version was still loaded in the same PHP process, and the two didn't fit together. It now finishes the update in a fresh process with the new code. Updates from the admin screen were never affected.
• php flarum millwright:update --resume finishes a run that stopped during "Finishing up", by starting that phase again from its first step. If an earlier self-update from the command line stopped there, this completes it.

composer update ernestdefoe/millwright
php flarum cache:clear

v1.25.0 — Flarum's conventions, tighter security

Changed

• Built the way Flarum's own extensions are, after a review by the Flarum team, since this becomes Flarum's Extension Manager in 2.1:
  • The screen uses Flarum's own buttons, alerts and dialogs. Confirmations open a dialog instead of the browser's pop-up, and problems show as Flarum alerts.
  • Colours come from your theme throughout, so dark mode and custom themes look right everywhere.
  • Errors reach the screen through Flarum's error handling, in your forum's language.

Security

• Downloads only ever use HTTPS, including after a redirect, and a token is only sent to the exact host it belongs to.
• auth.json is no longer backed up (its writes are atomic), and old copies are removed. Other backups keep the original file's permissions.
• Repository addresses with a username or token in them are never shown back in the browser.
• On hosts that can't run separate processes, updating Flarum itself no longer sends the database credentials over the network. A one-time token is used instead.

Fixed

• The flag that clears PHP's compiled-code cache can no longer get stuck if it was created by root, and checking for it costs one file check per request.

composer update ernestdefoe/millwright
php flarum cache:clear

v1.24.0 — progress in one bar

Changed

• An update's progress is one bar in sections. The phases (working out what changes, downloading, swapping files in, finishing up) used to be a row of pills, which read like tags. They are now a single tracker: finished phases are ticked, the current one is filled in your theme's colour and fills further as its steps finish, and the ones still to come are numbered. On a phone only the current phase keeps its label, so the bar never wraps. Thanks to ClaudiusH for the design.

composer update ernestdefoe/millwright
php flarum cache:clear

v1.23.3 — removals that can't take the site down

Fixed

• Removing an extension that loads a file on every request no longer takes the forum down partway through. Some extensions ask Composer to load a file on every request. When Millwright moved such an extension away, every request after that failed, including Millwright's own next step, so the removal could neither finish nor be undone. Millwright now stops Composer loading those files in the same moment it moves them. Thanks to ClaudiusH, who hit this removing RTL Support.
• A cache made unwritable during an update no longer stops it at "Clearing caches". If php flarum cache:clear is run as root while an update is waiting, the files it leaves are moved aside, as they already were before an update starts.
• Counts read properly: "1 package has a newer version", "19 packages have a newer version", instead of "package(s)". Thanks to ClaudiusH.

composer update ernestdefoe/millwright
php flarum cache:clear

v1.23.2 — updates finish on 128 MB hosts

Fixed

• Updates no longer fail at the very end on hosts with a 128 MB PHP memory limit. In Flarum 2, cache:clear rebuilds every frontend's CSS in one go, and the memory that takes grows with the extensions you have enabled: about 600 MB on a forum with many of them. On a host whose command-line PHP is capped at 128 MB, every update stopped at "clear caches". Millwright now runs Flarum's commands without that cap, the same way it already runs Composer. Thanks to Wil Vincent for sending the full error.

composer update ernestdefoe/millwright
php flarum cache:clear

If php flarum cache:clear itself runs out of memory on your host, run it as php -d memory_limit=-1 flarum cache:clear.

v1.23.1 — failures show the error, not just the trace

Fixed

• When a Flarum command fails during an update, the message now shows the line that says what went wrong. It used to show only the last twelve lines of output. PHP and Xdebug print the error first and the stack trace after it, so the error itself was cut off and only the trace was left. Now you get the first lines and the last, with each line kept short. Thanks to Wil Vincent, whose cache:clear failure came through as twelve lines of trace and no error.
• A rollback that fails at one of these commands now says why. It used to name the command and nothing else.

composer update ernestdefoe/millwright
php flarum cache:clear