Resources

Release notes - Acquia Dev Desktop

Important

End of Support notice! Acquia has stopped support for Dev Desktop on June 30, 2021. Acquia recommends that you transition to Cloud IDE for a managed development environment on Cloud Platform. For more information, see Migrating from Dev Desktop to Cloud IDE.

Acquia also provides limited integration with open source alternatives to Cloud IDE for local development. For more information, see Local development solutions.

This webpage describes the regular updates Acquia has made to Acquia Dev Desktop.

For a list of known issues you may encounter when using Acquia Dev Desktop, see Known issues in Acquia Dev Desktop.

For installation instructions for Acquia Dev Desktop, see Installing Acquia Dev Desktop.

If you encounter any difficulties with your Acquia Dev Desktop subscription, contact Acquia Support for assistance.

Acquia Dev Desktop - September 30, 2020

  • Feature Dev Desktop on Windows can now push Drupal 9.0.3 sites to Acquia Cloud Platform.

  • Fix When IP allowlisting was enabled on a customer application, Acquia Dev Desktop displayed an unclear error message.

Acquia Dev Desktop - August 12, 2020

  • Change Acquia Dev Desktop 2 no longer supports PHP 7.0 and 7.1.

  • Change Acquia Dev Desktop now defaults to latest PHP version.

  • Fix When the Dev Desktop is launched, MySQL database server failed to start.

Acquia Dev Desktop - July 9, 2020

  • Change The Acquia Dev Desktop installer now requests additional user information to help Acquia Support and marketing.

  • Change While generating an SSH key pair in Acquia Dev Desktop on Windows, the Settings window displays a passphrase prompt for users of the new SSH client.

  • Change Acquia Dev Desktop no longer allows you to push Composer-based Drupal 8 sites to the Cloud Platform, unless you have committed all dependencies and ensured they’re not in the gitignore file.

  • Fix The default PHP version would roll back after importing a site from Cloud Platform.

Acquia Dev Desktop - May 14, 2020

  • Change For Drupal 9 compatibility, Acquia Dev Desktop now includes support for Drush 10.

  • Change For Drupal 9 compatibility, Acquia Dev Desktop now includes support for MySQL version 5.7.

Important

This release appears to have installation issues for macOS Catalina. If you are a Catalina user, Acquia recommends not updating Acquia Dev Desktop at this time.

Acquia Dev Desktop - March 20, 2020

  • Fix Some users couldn’t change the default PHP version for their applications.

  • Fix Users with capital letters in their email address (as registered on acquia.com) couldn’t use Cloud API v2.

Acquia Dev Desktop - March 18, 2020

  • Change Acquia Dev Desktop 2 now supports Acquia Cloud API v2. For your Acquia Dev Desktop subscription to continue working as expected after July 1, 2020 (when Acquia Cloud API v1 reaches end-of-life) you must update your version of Acquia Dev Desktop and reconfigure it to use Acquia Cloud API v2.

  • Change Acquia Dev Desktop 2 no longer supports PHP 5.5 or PHP 5.6.

  • Fix For subscribers importing a website from Acquia Cloud, the Acquia Dev Desktop 2 user interface displayed alphanumeric URLs rather than application names when displaying the names of websites.

Acquia Dev Desktop - February 3, 2020

Important

Acquia Dev Desktop subscribers must update to Acquia Dev Desktop 2 by March 7, 2020. After this date, the older, deprecated version of Acquia Dev Desktop will no longer be able to upload or download files, databases, and code to or from Acquia Cloud. Although everything will still work locally, the older version will have degraded functionality and won’t operate as expected with Acquia Cloud. Subscribers who don’t update to Acquia Dev Desktop 2 by March 7, 2020, may receive warnings about a security issue. To download the latest version, access Acquia Dev Desktop.

  • Change Subscribers using Windows 10 can now SSH to FIPS compliant servers in Acquia Dev Desktop 2.

  • Change The certificate used to sign Windows releases was updated.


The information contained herein is subject to change without notice and is not warranted to be error-free. If you encounter any errors, contact Acquia Support.