Releases: Varying-Vagrant-Vagrants/VVV
Releases · Varying-Vagrant-Vagrants/VVV
3.4.1
3.3.0
3.2.0
3.1.1
3.1.0
3.0.0
2.6.0
2.5.1
VVV 2.2.1
VVV 2.1.0
Enhancements
- Add cosmetic improvements to provisioning. This cleans up quite a bit of the junk that displayed on many lines when it should have displayed on one. See #1247.
- Update ack-grep to 2.16. See #1148.
- Dashboard (
http://vvv.test) links now open in new tabs. See #1168. - Speed up checking for
vvv-hostsfiles inVagrantfile. See #1182. - Pass more configuration data to the VirtualBox VM on boot. See #1197.
- Link to
varyingvagrantvagrants.org's Add New Site in thehttp://vvv.testdashboard. See #1220. - Build the VirtualBox VM name from the Vagrant directory and path hash. See #1236.
- PHPCS is now installed via Composer. See #922.
- VVV now uses .test instead of .dev for new installs and the dashboard. See #583.
- Added the VIP minimum coding standards to PHPCS. See #1279.
Bugs
- Fix a wrong path for phpcs and phpcbf executables. See #1200.
- Force Composer to use the
scriptsdirectory instead ofbin. See #1202. - Fix bug installing
rvm(which broke MailCatcher). See #1235. - Add
phpcodesniffer-standardto PHPCS'scomposer.json. See #1239. - Ignore provision generated PHPCS files in Git. See #1276.
Documentation
Many updates to VVV's documentation were made between the release of 2.0.0 and now. As of 2.1.0, the process to contributing to documentation has changed to use the varyingvagrantvagrants.org repository. This allows the workflow for shipping documentation changes to proceed separately from shipping VVV releases.