You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Switch to using npm over yarn
Signed-off-by: Janne Savolainen <[email protected]>
* Remove reference to `yarn` from documentation
Signed-off-by: Sebastian Malton <[email protected]>
* Enable NPM workspaces
Co-authored-by: Mikko Aspiala <[email protected]>
Signed-off-by: Janne Savolainen <[email protected]>
* Introduce script for installing all dependencies
Co-authored-by: Mikko Aspiala <[email protected]>
Signed-off-by: Janne Savolainen <[email protected]>
* Remove usage of lerna bootstrap for no longer being used
Co-authored-by: Mikko Aspiala <[email protected]>
Signed-off-by: Janne Savolainen <[email protected]>
* Fix build by not bundling libraries for application in node environment (main) as Electron does that
Co-authored-by: Mikko Aspiala <[email protected]>
Signed-off-by: Janne Savolainen <[email protected]>
* Tweak evil static import paths in build of application
Co-authored-by: Mikko Aspiala <[email protected]>
Signed-off-by: Janne Savolainen <[email protected]>
* Consolidate npmrc configs to root since required by workspaces
Co-authored-by: Mikko Aspiala <[email protected]>
Signed-off-by: Janne Savolainen <[email protected]>
* Make application build not fail for not detecting electron version
Signed-off-by: Janne Savolainen <[email protected]>
* Update package-lock
Signed-off-by: Janne Savolainen <[email protected]>
* Make sure native dependencies are rebuilt for electron
Signed-off-by: Janne Savolainen <[email protected]>
* Remove unused binary for causing trouble when installing dependencies
Signed-off-by: Janne Savolainen <[email protected]>
* Update package-lock
Signed-off-by: Janne Savolainen <[email protected]>
* Disable caching in CI for Windows
Installing Electron in Windows seems to be broken in this regards.
Signed-off-by: Janne Savolainen <[email protected]>
---------
Signed-off-by: Janne Savolainen <[email protected]>
Signed-off-by: Sebastian Malton <[email protected]>
Co-authored-by: Sebastian Malton <[email protected]>
Copy file name to clipboardExpand all lines: RELEASE_GUIDE.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -5,15 +5,15 @@ All releases will be made by creating a PR which bumps the version field in the
5
5
6
6
## Prerequisites
7
7
8
-
-`yarn`
9
-
- Running `yarn` (to install all dependencies)
8
+
-`npm`
9
+
- Running `npm install`
10
10
-`gh` (Github's CLI) with a version at least 2.15.0
11
11
12
12
## Steps
13
13
14
14
1. If you are making a minor or major release (or prereleases for one) make sure you are on the `master` branch.
15
15
1. If you are making a patch release (or a prerelease for one) make sure you are on the `release/v<MAJOR>.<MINOR>` branch.
16
-
1. Run `yarn create-release-pr <release-type>`. If you are making a subsequent prerelease release, provide the `--check-commits` flag.
16
+
1. Run `npm run create-release-pr <release-type>`. If you are making a subsequent prerelease release, provide the `--check-commits` flag.
17
17
1. If you are checking the commits, type `y<ENTER>` to pick a commit, and `n<ENTER>` to skip it. You will want to skip the commits that were part of previous prerelease releases.
18
18
1. Once the PR is created, approved, and then merged the `Release Open Lens` workflow will create a tag and release for you.
19
19
1. If you are making a major or minor release, create a `release/v<MAJOR>.<MINOR>` branch and push it to `origin` so that future patch releases can be made from it.
0 commit comments