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

RELEASE GUIDE: fix formatting, add a clarification (#4230)

Browse Source
This commit is contained in:
Jim Ehrismann 2021-11-03 10:17:21 -04:00 committed by GitHub
parent f6503a6596
commit 0ae4dfbeab
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
RELEASE_GUIDE.md
View File

@ -10,9 +10,9 @@ Lens releases are built by CICD automatically on git tags. The typical release p
- `major` - `major`
- `minor` - `minor`
- `patch` - `patch`
- `premajor` [--preid=<prerelease-id>] - `premajor [--preid=<prerelease-id>]`
- `preminor` [--preid=<prerelease-id>] - `preminor [--preid=<prerelease-id>]`
- `prepatch` [--preid=<prerelease-id>] - `prepatch [--preid=<prerelease-id>]`
- `prerelease [--preid=<prerelease-id>]` - `prerelease [--preid=<prerelease-id>]`
where `<prerelease-id>` is generally one of: where `<prerelease-id>` is generally one of:
@ -28,6 +28,8 @@ Lens releases are built by CICD automatically on git tags. The typical release p
- `git tag -fa vX.Y.Z-beta.N` (move the tag locally to the current commit) - `git tag -fa vX.Y.Z-beta.N` (move the tag locally to the current commit)
- `git push origin --tags` (update the tags on https://github.com/lensapp/lens to reflect this local change) - `git push origin --tags` (update the tags on https://github.com/lensapp/lens to reflect this local change)
Once the tag has been updated on origin (e.g. by `git push origin --tags`) the azure jobs are automatically triggered again.
1. Once CI passes again go to the releases tab on GitHub. You can use the existing draft release prepared by k8slens-bot (select the correct tag). Or you can create a new release from the tag that was created, and make sure that the change log is the same as that of the PR, and the title is the tag. Either way, click the prerelease checkbox if this is not a new major, minor, or patch version before clicking `Publish release`. 1. Once CI passes again go to the releases tab on GitHub. You can use the existing draft release prepared by k8slens-bot (select the correct tag). Or you can create a new release from the tag that was created, and make sure that the change log is the same as that of the PR, and the title is the tag. Either way, click the prerelease checkbox if this is not a new major, minor, or patch version before clicking `Publish release`.
1. Merge the release PR after the release is published. If it is a patch release then there is no need to squash the cherry-picked commits as part of the merge. GitHub should delete the branch once it is merged. 1. Merge the release PR after the release is published. If it is a patch release then there is no need to squash the cherry-picked commits as part of the merge. GitHub should delete the branch once it is merged.
1. If you have just released a new major or minor version then create a new `release/vMAJOR.MINOR` branch from that same tag and push it to https://github.com/lensapp/lens. Given the commit of the merged release PR from the master branch you can do this like 1. If you have just released a new major or minor version then create a new `release/vMAJOR.MINOR` branch from that same tag and push it to https://github.com/lensapp/lens. Given the commit of the merged release PR from the master branch you can do this like