beckermj/vaguerent
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update new release steps

Browse Source
This commit is contained in:
Chris Roberts 2023-10-16 09:25:14 -07:00
parent 1bd952a598
commit b8f9efb0d2
1 changed files with 3 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
RELEASE.md
View File

@ -4,34 +4,8 @@ This documents how to release Vagrant. Various steps in this document will
require privileged access to private systems, so this document is only require privileged access to private systems, so this document is only
targeted at Vagrant core members who have the ability to cut a release. targeted at Vagrant core members who have the ability to cut a release.
1. Update `version.txt` to the version you want to release. 1. Go to the [release initiator workflow](https://github.com/hashicorp/vagrant/actions/workflows/initiate-release.yml)
1. Update `CHANGELOG.md` to have a header with the release version and date. 1. Trigger a new run with the version to be released (it should not include a `v` prefix, for example: `1.0.0`)
1. Commit those changes and also tag the release with the version: 1. After release is complete, update [Checkpoint](https://checkpoint.hashicorp.com/control)
```
$ git tag vX.Y.Z
$ git push --tags
```
1. This will automatically trigger an installer creation, upload the artifacts,
and publish the release.
1. After the release has been published update the `website/config.rb` to point
to the latest version, commit, and push.
1. Publish the webiste by deleting the `stable-website` branch, recreate the branch,
and force push. From the `main` branch, run:
```
$ git branch -D stable-website
$ git branch -b stable-website
$ git push -f origin stable-website
```
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.