Skip to content

v1.16.4: xdebug 3 that works with composer 2 :) (Bug fix)
Compare
Choose a tag to compare
@rfay rfay released this 14 Dec 23:14
· 1908 commits to master since this release
v1.16.4
a7d5c6a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Installation/Upgrade

See the installation instructions for details, but it's easy:

  • Please stop all projects first, this does no harm: ddev poweroff
  • macOS Homebrew and Linux Linuxbrew: brew install drud/ddev/ddev or just brew upgrade drud/ddev/ddev ). (You may need a brew update for homebrew to find the new release.)
  • Windows: Use choco upgrade -y ddev to get this one, or download the ddev_windows_installer below.
  • Linux and macOS with the install_ddev.sh script: curl -LO https://raw.githubusercontent.com/drud/ddev/master/scripts/install_ddev.sh && bash install_ddev.sh
  • And anywhere, you can just download the tarball or zipball, untar or unzip it, and place the executable in your path where it belongs.
  • Consider ddev delete images after upgrading to free up disk space used by previous docker image versions. This does no harm.

Key changes in v1.16.4

This is the same as v1.16.3, but fixes a bug where people who were using composer_version: "2" couldn't use xdebug. Stranger than fiction.

  • For the big stuff in v1.16, please read v1.16.0 release notes
  • Xdebug 3.0.1 is included with PHP 7.2/7.3/7.4/8.0! It's much faster and has been getting rave reviews
  • PHPMyAdmin (ddev launch -p) now logs into the database as the root user instead of the db user

Why did we need a release for Xdebug 3? It was because the upstream deb.sury.org packages made their planned shift to xdebug 3 for PHP7.2/3/4. Before long, all ddev users who used webserver_extra_packages or did an apt-get install in a custom Dockerfile would have been seeing significant breakage, since the Xdebug config is completely different. And also, of course, people have been looking forward to a faster Xdebug 3.

Caveats

The configuration for Xdebug 3 is different from Xdebug 2. This doesn't affect the vast majority of people, but if you have custom PHP configuration in your project that changes xdebug.*, it will need to be updated. See the Xdebug 2->3 Upgrade Guide if this is you. Almost nobody needs to touch anything, as ddev already chooses the right config for the right Xdebug version.

Commits since v1.16.3

a7d5c6a Fix syntax errors in xdebug custom command (#2694)
3e5ff3e Use XDEBUG_MODE to disable xdebug in Dockerfile, not disable_xdebug (#2693)
a089dc9 [docs] Clarify that ddev xdebug should be executed in project directory (#2692) [skip ci][ci skip]

Assets 22