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
6a43f901b3
lens/RELEASE_GUIDE.md
Juho Heikka 1d78912dd8
Release 6.4.2 (#7286) 
* Fix request namespace list permissions check if a list rule is not the first match (#7282)

Signed-off-by: Jari Kolehmainen <jari.kolehmainen@gmail.com>

* Fix cluster metadata detectors (#7255)

Signed-off-by: Juho Heikka <juho.heikka@gmail.com>

* Fix extension API not having all the correct types (#7263)

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

* Update release guide and fix release script (#7276)

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

* Release 6.4.2

Signed-off-by: Juho Heikka <juho.heikka@gmail.com>

---------

Signed-off-by: Jari Kolehmainen <jari.kolehmainen@gmail.com>
Signed-off-by: Juho Heikka <juho.heikka@gmail.com>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Co-authored-by: Sebastian Malton <sebastian@malton.name>
2023-03-06 13:01:42 +02:00

1.5 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 of 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 npm run create-release-pr.
  4. Pick the PRs that you want to include in this release using the keys listed.
  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.
  7. 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.
  8. If you released a patch version, create a new patch milestone for the next patch version and move all the issues and PRs (open or closed) that weren't included in the current release to that milestone.
  9. Close the milestone related to the release that was just made (if not a prerelease release).