From b8f9efb0d2841c47f8f9a77f02d7fbcbaa62a664 Mon Sep 17 00:00:00 2001 From: Chris Roberts Date: Mon, 16 Oct 2023 09:25:14 -0700 Subject: [PATCH] Update new release steps --- RELEASE.md | 32 +++----------------------------- 1 file changed, 3 insertions(+), 29 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index c3224aabdc4..1ebde5409f3 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -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 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: - - ``` - $ 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. +1. After release is complete, update [Checkpoint](https://checkpoint.hashicorp.com/control)