<commit_before>---
page_title: "Configuration Version - Vagrantfile"
sidebar_current: "vagrantfile-version"
---

# Configuration Version

Configuration versions are the mechanism by which Vagrant 1.1+ is able
to remain [backwards compatible](v2/installation/backwards-compatibility.html)
with Vagrant 1.0.x Vagrantfiles, while introducing dramatically new features
and configuration options.

If you run `vagrant init` today, the Vagranfile will be in roughly the
following format:

```ruby
VAGRANTFILE_API_VERSION = "2"
<commit_msg>Fix typo<commit_after>---
page_title: "Configuration Version - Vagrantfile"
sidebar_current: "vagrantfile-version"
---

# Configuration Version

Configuration versions are the mechanism by which Vagrant 1.1+ is able
to remain [backwards compatible](v2/installation/backwards-compatibility.html)
with Vagrant 1.0.x Vagrantfiles, while introducing dramatically new features
and configuration options.

If you run `vagrant init` today, the Vagrantfile will be in roughly the
following format:

```ruby
VAGRANTFILE_API_VERSION = "2"

{'fraction_non_alphanumeric': 0.07909604519774012, 'fraction_numerical': 0.011299435028248588, 'mean_word_length': 5.727848101265823, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '249339', 'n_tokens_mistral': 321, 'n_tokens_neox': 310, 'n_words': 109}