2016-06-10 18:11:10 +00:00
|
|
|
# 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
|
2018-02-06 19:20:29 +00:00
|
|
|
targeted at Vagrant core members who have the ability to cut a release.
|
2016-06-10 18:11:10 +00:00
|
|
|
|
2016-06-14 18:33:19 +00:00
|
|
|
1. Update `version.txt` to the version you want to release.
|
2016-06-10 18:11:10 +00:00
|
|
|
|
2016-06-14 18:33:19 +00:00
|
|
|
1. Update `CHANGELOG.md` to have a header with the release version and date.
|
2016-06-10 18:11:10 +00:00
|
|
|
|
2016-06-14 18:33:19 +00:00
|
|
|
1. Commit those changes and also tag the release with the version:
|
2016-06-10 18:11:10 +00:00
|
|
|
|
2016-06-14 18:33:19 +00:00
|
|
|
```
|
|
|
|
$ git tag vX.Y.Z
|
|
|
|
$ git push --tags
|
|
|
|
```
|
2016-06-10 18:11:10 +00:00
|
|
|
|
2019-06-25 21:26:37 +00:00
|
|
|
1. This will automatically trigger an installer creation, upload the artifacts,
|
|
|
|
and publish the release.
|
2016-06-10 18:11:10 +00:00
|
|
|
|
2019-06-25 21:26:37 +00:00
|
|
|
1. After the release has been published update the `website/config.rb` to point
|
|
|
|
to the latest version, commit, and push.
|
2016-06-10 18:11:10 +00:00
|
|
|
|
2019-06-25 21:26:37 +00:00
|
|
|
1. Publish the webiste by deleting the `stable-website` branch, recreate the branch,
|
|
|
|
and force push. From the `master` branch, run:
|
2016-06-10 18:11:10 +00:00
|
|
|
|
2019-06-25 21:26:37 +00:00
|
|
|
```
|
|
|
|
$ git branch -D stable-website
|
|
|
|
$ git branch -b stable-website
|
|
|
|
$ git push -f origin stable-website
|
|
|
|
```
|
2016-06-14 18:33:19 +00:00
|
|
|
|
|
|
|
1. Update `version.txt` to append `.dev` and add a new blank entry in the
|
|
|
|
CHANGELOG, commit, and push.
|
|
|
|
|
|
|
|
1. Update [Checkpoint](https://checkpoint.hashicorp.com/control) with the new
|
|
|
|
version.
|