website/content/docs/installation/upgrading.mdx
⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️
[!IMPORTANT]
Documentation Update: Product documentation previously located in/websitehas moved to thehashicorp/web-unified-docsrepository, where all product documentation is now centralized. Please make contributions directly toweb-unified-docs, since changes to/websitein this repository will not appear on developer.hashicorp.com. ⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️
This page details how to upgrade Vagrant in the 1.x.x series.
~> If you need to upgrade from Vagrant 1.0.x, read the specific page dedicated to that.
Vagrant upgrades during the 1.x.x release series are straightforward:
The installers will properly overwrite and remove old files. It is recommended that no other Vagrant processes are running during the upgrade process.
Note that Vagrantfile stability for the new Vagrantfile syntax is not guaranteed until Vagrant 3.0. While Vagrantfiles made for 1.0.x will continue to work, newer Vagrantfiles may have backwards incompatible changes until 3.0.
If you encounter any problems at upgrade time, report them as an issue in Github. Upgrades are meant to be a smooth process and we consider it a bug if it was not.