From a6e0da12971e3a763ff33dac14079c8a06e15eed Mon Sep 17 00:00:00 2001 From: Sebastian Malton Date: Thu, 23 Mar 2023 07:34:02 -0400 Subject: [PATCH] Fix formatting in release guide (#7398) Signed-off-by: Sebastian Malton --- RELEASE_GUIDE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/RELEASE_GUIDE.md b/RELEASE_GUIDE.md index f89bfa3295..d46911b0ce 100644 --- a/RELEASE_GUIDE.md +++ b/RELEASE_GUIDE.md @@ -15,8 +15,8 @@ All releases will be made by creating a PR which bumps the version field in the 1. If you are making a patch release (or a prerelease for one) make sure you are on the `release/v.` branch. 1. Run `npm run create-release-pr`. 1. Pick the PRs that you want to include in this release using the keys listed. - - If you are making a patch release this might include fixing up some cherry-picking of commits. These actions should be done in a separate terminal. - - If a package version is having a major version bump then `npm` will complain about `peerDependency` conflicts. These will have to be fixed up separately. + - If you are making a patch release this might include fixing up some cherry-picking of commits. These actions should be done in a separate terminal. + - If a package version is having a major version bump then `npm` will complain about `peerDependency` conflicts. These will have to be fixed up separately. 1. Once the PR is created, approved, and then merged the `Release Open Lens` workflow will create a tag and release for you. 1. If you are making a major or minor release, create a `release/v.` branch and push it to `origin` so that future patch releases can be made from it. 1. If you released a major or minor version, create a new patch milestone and move all bug issues to that milestone and all enhancement issues to the next minor milestone.