hendrik/lens
1
0
Fork 0
mirror of https://github.com/lensapp/lens.git synced 2025-05-20 05:10:56 +00:00
Code Issues Projects Releases Wiki Activity
28728aeee4
lens/RELEASE_GUIDE.md
Sebastian Malton 11e7a38823
Release 6.1.11 (#6397) 
* Release 6.1.11

Signed-off-by: Sebastian Malton <sebastian@malton.name>

* Add release guide (#6374)

Signed-off-by: Sebastian Malton <sebastian@malton.name>

Signed-off-by: Sebastian Malton <sebastian@malton.name>

* Fix crash when opening pod details (#6376)

Signed-off-by: Sebastian Malton <sebastian@malton.name>

Signed-off-by: Sebastian Malton <sebastian@malton.name>

* Fix ReactiveDuration to update as frequently as necessary (#6375)

- When used in non compact mode (eg KubeObjectMeta's age) the seconds
  can be displayed but previously between 10m and 180m of age, the
  display would only update every minute

Signed-off-by: Sebastian Malton <sebastian@malton.name>

Signed-off-by: Sebastian Malton <sebastian@malton.name>

Signed-off-by: Sebastian Malton <sebastian@malton.name>
2022-10-11 11:39:33 -04:00

1.2 KiB
Raw Blame History

Release Guide

Releases for this repository are made via running the create-release-pr script defined in the package.json. All releases will be made by creating a PR which bumps the version field in the package.json and, if necessary, cherry pick the relavent commits from master.

Prerequisites

  • yarn
  • Running yarn (to install all dependencies)
  • 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.
  2. If you are making a patch release (or a prerelease for one) make sure you are on the release/v<MAJOR>.<MINOR> branch.
  3. Run yarn create-release-pr <release-type>. If you are making a subsequent prerelease release, provide the --check-commits flag.
  4. 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.
  5. Once the PR is created, approved, and then merged the Release Open Lens workflow will create a tag and release for you.
  6. 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.