From 3d10a9e8fcb411de65178af00207fe2d5462a8c1 Mon Sep 17 00:00:00 2001 From: Sebastian Malton Date: Fri, 17 Feb 2023 13:36:01 -0500 Subject: [PATCH] Remove reference to `yarn` from documentation Signed-off-by: Sebastian Malton --- RELEASE_GUIDE.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/RELEASE_GUIDE.md b/RELEASE_GUIDE.md index 559385f025..01969bbbee 100644 --- a/RELEASE_GUIDE.md +++ b/RELEASE_GUIDE.md @@ -5,15 +5,15 @@ All releases will be made by creating a PR which bumps the version field in the ## Prerequisites -- `yarn` -- Running `yarn` (to install all dependencies) +- `npm` +- Running `npm install` - `gh` (Github's CLI) with a version at least 2.15.0 ## Steps 1. If you are making a minor or major release (or prereleases for one) make sure you are on the `master` branch. 1. If you are making a patch release (or a prerelease for one) make sure you are on the `release/v.` branch. -1. Run `yarn create-release-pr `. If you are making a subsequent prerelease release, provide the `--check-commits` flag. +1. Run `npm run create-release-pr `. If you are making a subsequent prerelease release, provide the `--check-commits` flag. 1. If you are checking the commits, type `y` to pick a commit, and `n` to skip it. You will want to skip the commits that were part of previous prerelease releases. 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.