OCram85/code-server
Archived
1
0
Fork 0
Code Pull Requests 2 Activity

refactor(ci): use release in branch release name (#5352)

Browse Source
This commit is contained in:
Joe Previte
2022-07-18 14:38:07 -07:00
committed by GitHub
parent 033cdf2357
commit 23a18786de
2 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/MAINTAINING.md
View File

@ -164,7 +164,8 @@ If you're the current release manager, follow these steps:
### Publishing a release
1. Create a new branch called `v0.0.0` (replace 0s with actual version aka v4.5.0)
1. Create a new branch called `release/v0.0.0` (replace 0s with actual version aka v4.5.0)
1. If you don't do this, the `npm-brew` GitHub workflow will fail. It looks for the release artifacts under the branch pattern.
1. Run `yarn release:prep` and type in the new version (e.g., `3.8.1`)
1. GitHub Actions will generate the `npm-package`, `release-packages` and
`release-images` artifacts. You do not have to wait for this step to complete