Releasing Vagrant

This documents how to release Vagrant. Various steps in this document will require privileged access to private systems, so this document is only targetted at Vagrant core members who have the ability to cut a release.

Update version.txt to the version you want to release.
Update CHANGELOG.md to have a header with the release version and date.
Commit those changes and also tag the release with the version:
```
$ git tag vX.Y.Z
$ git push --tags
```
Trigger an installer creation run within the HashiCorp Bamboo installation. This will take around 45 minutes.
Download all the resulting artifacts into the pkg/dist folder relative to the Vagrant repository on your local machine.
Run ./scripts/sign.sh with the version that is being created. This must be run from the Vagrant repo root. This will GPG sign and checksum the files.
Run the following command to upload the binaries to the releases site:
```
$ hc-releases upload pkg/dist
```
Publish the new index files to the releases site:
```
$ hc-releases publish
```
Update website/config.rb to point to the latest version, commit, and push.
Tell HashiBot to deploy in ``#deploys`
```
hashibot deploy vagrant
```
Update version.txt to append .dev and add a new blank entry in the CHANGELOG, commit, and push.
Update Checkpoint with the new version.

1.5 KiB Raw Blame History

Releasing Vagrant

1.5 KiB

Raw Blame History