1.0.7

Well, 💩! That sure didn't work.

1.0.6 immediately proved to be a paper-bag release, and now we're wondering if this project isn't under some kind of inverted Star Trek movie curse (traditionally, the even-numbered ones are good and odd-numbered ones are bad). Can we stop stepping on rakes half the time? Tune in to v1.0.8 to find out!

Snark aside, this release reverts #203, which broke the app for everybody. Back to the drawing board with that one.

1.0.6

This release is mostly housekeeping (i.e., updating dependencies), but two bugs were fixed:

• #201: Runs PHP with a higher memory limit than it would run with by default. This is helpful for Drupal, which can in some situations be pretty hefty.
• #202: Fixes a bug where reinstalling Drupal would give you stale dependencies.

1.0.5

😐 Welp, 1.0.4 turned out to be a paper bag release (if you're unfamiliar, a paper bag release is a release that is totally broken for everybody), so here's a new one!

This does make a couple of changes when setting up new Drupal sites:

• default.settings.php is no longer changed; instead, settings.php is created immediately with the necessary alterations.
• One of those alterations is that configuration is always exported, by default, into a config directory next to the web root. This is generally a best practice for Drupal sites.

1.0.4

This release is mostly housekeeping and refactoring, but it includes a new feature: a dedicated button to clear the Drupal cache (#187, #188, and #191). You can do that from the Drupal user interface, of course, but what if Drupal is totally broken and you need drush cache:rebuild? Well...that's what the button is for. 😎

1.0.3

There are two changes of note in this version:

• #177 added the underlying plumbing needed to make the app international. Drupal speaks your language; the launcher should too! At the moment, only English is available but we now have a clear path to add more languages.
• Switched to PHP 8.4, which is the current recommended version for Drupal 11.

Beyond that, there were a few dependency updates; nothing exciting.

1.0.2

• #169: Silenced an error that would be reported when checking for updates on macOS if the app was not copied into the system's Applications folder (as per documentation).
• Set a 5-minute maximum execution time for each request to the built-in PHP web server.

1.0.1

Disabled automatic crash reporting when the app is running unpackaged. This will help us diagnose problems because intentional test-only problems and failures will no longer be reported.

1.0.0

First. Stable. Release! 🎉

No real changes in this one since beta1, apart from some light maintenance and documentation changes.

1.0.0-beta1

• In addition to the handy trash button, we added a button that will open the Drupal directory in your file explorer. (#155)
• While installing Drupal -- either from a pre-built archive or via Composer -- you'll see an actual, accurate progress bar. (#157)

Plus the usual housekeeping; some refactoring, some minor UX improvements...

v1.0.0-alpha15

Lots of changes in this one. Some of the most notable:

• The launcher now has a button that lets you delete the Drupal site and recreate it. It doesn't look all that good (yet!) but it works just fine. A very useful feature -- no longer do you need to bushwhack your way through dusty corners of your hard drive to locate the Drupal site when you want to get rid of it. (#149)
• We finally documented what to do when Windows Firewall blocks the launcher. (#146)
• When Composer encounters an error, its contents will now be surfaced in the UI for easier debugging and error reporting. (#142)
• As part of implementing automatic updates, a version number is now recorded in composer.json when Drupal CMS is spun up. This doesn't affect the user experience at all but it will allow future releases to make necessary changes to the project without you needing to touch the command line. (#141)
• When extracting Drupal CMS from a pre-built archive (default behavior), you'll now get an accurate progress indicator instead of an endless "please wait" message. (#138)
• There's been a ton of refactoring -- certain internal patterns have changed, and the UI is now written in Svelte.