2.7.0

Changed

• Removed the install wizard option to copy the Ansible roles into your project and customize. This can still be done, but in almost all cases adding a custom playbook is more maintainable. Existing setups that use this approach will continue to work. (PR #76)

No update steps are required.

2.6.2

Fixed

• Update expired package sources on the drupalbox (fixes for drupalbox 1.4.0 and below, and 2.0.0)

No update steps are required.

Note: If you chose the option to "Copy Ansible roles into your project for customization" during installation, you will need to manually copy the new steps into the "common" role. (See https://github.com/palantirnet/the-vagrant/pull/75/files.)

2.6.1

Fixed

• Ansible 2.9 compatibility

No update steps are required.

2.6.0

Changed

• Removed user-specific provisioning and zsh configuration (#72)

This functionality is no longer used by our team, and causes issues with Mac OS 10.15 Catalina. No update steps are required.

2.5.2

Fixed

• The drupal-check installation was failing because ~/bin did not yet exist.

No update steps are required.

2.5.1

Added

• Added a trigger to the default Vagrantfile that keeps the installed version of Composer up to date (#68)

Changed

• Removed the custom drush wrapper in ~/bin. Drush 9 handles this itself.
• Removed the vagrant up trigger that ran composer install on the project

Updating from 2.5

• This update does not require destroying your current vagrant box.
• This version includes changes to the Vagrantfile template. To get these changes, either re-run the-vagrant's installer with vendor/bin/the-vagrant-installer, OR manually apply the changes from the diff from #70.
• As a developer, you may also want to:
  1. From your Vagrant box, rm ~/bin/drush
  2. Log out of your vagrant and then back in before continuing to work

2.5.0

Changed

• Switched the Ansible Galaxy role used to install nvm, since the previous role isn't compatible with Ansible 2.9

Updating from 2.4.0

• No changes to your project are required.
• This update does not require destroying your current vagrant box.

2.4.0

Added

• Installed drupal-check globally on the VM to prepare for Drupal 9 (#63)

Changed

• Disabled audio on the VM to avoid a performance bug (#60)

Updating from 2.3.0

This version includes changes to the Vagrantfile template. To get these changes, either re-run the-vagrant's installer with vendor/bin/the-vagrant-installer, OR manually apply the changes from the diff from #60.

You will also need to re-run the provisioning with vagrant reload --provision; this will add drupal-check to your existing box.

This update does not require destroying your current vagrant box.

2.3.0

Changed

• The template Vagrantfile was changed to allow downloading roles from Ansible Galaxy

Added

• Provisioning now installs nvm, using the leanbit.nvm role from Ansible Galaxy

Updating to 2.3.0

1. Updating to this version requires updates to your project's Vagrantfile:
2. Re-run the-vagrant's installer with vendor/bin/the-vagrant-installer to get the latest version; this will overwrite any customizations you've made.
3. - OR - Add the changes to the Vagrantfile shown in PR #56 (the current default Node version is 8)
4. Re-run the provisioning with vagrant reload --provision; this will add nvm to your existing box.

This update does not require destroying your current vagrant box.

2.2.2

Fixed

• Fixed an issue with generating the self-signed certificate for HTTPS support when there are extra_hostnames in the Vagrantfile

Added

• On provisioning, the git user name and email are now copied from the host into the .gitconfig on the VM

Updating from 2.2.1 or 2.2.0

• This update does not require destroying your current vagrant box.
• After updating a project to 2.2.2, run vagrant reload --provision