bughz
/
code-server
mirror of https://github.com/coder/code-server.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update release guide

This commit is contained in:
Asher 2023-02-07 13:43:28 -09:00
parent 71ff747c48
commit 82073743b1
No known key found for this signature in database
GPG Key ID: D63C1EF81242354A
1 changed files with 18 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
docs/MAINTAINING.md
View File

@ -142,24 +142,28 @@ changelog](https://github.com/emacs-mirror/emacs/blob/master/etc/NEWS).
### Publishing a release ### Publishing a release
1. Go to GitHub Actions > Draft release > Run workflow off commit you want to 1. Go to GitHub Actions > Draft release > Run workflow on the commit you want to
release. CI will automatically upload the artifacts to the release. Make sure CI release. Make sure CI has finished the build workflow on that commit or this
has finished on that commit. will fail.
1. CI will automatically grab the 2. CI will automatically grab the build artifact on that commit, inject the
artifacts, publish the NPM package from `npm-package`, and publish the Docker version into the `package.json`, put together platform-specific packages, and
Hub image from `release-images`. upload those packages to a draft release.
1. Publish release. 3. Summarize the major changes in the `CHANGELOG.md`.
1. After, create a new branch called `release/v0.0.0` (replace 0s with actual version aka v4.5.0) 4. Copy the relevant changelog section to the release then publish it.
1. Summarize the major changes in the `CHANGELOG.md` 5. CI will automatically publish the NPM package, Docker image, and update
1. Bump chart version in `Chart.yaml`. Homebrew using the published release assets.
6. Bump the chart version in `Chart.yaml` and merge in the changelog updates.
#### Release Candidates #### Release Candidates
We prefer to do release candidates so the community can test things before a full-blown release. To do this follow the same steps as above but: We prefer to do release candidates so the community can test things before a
full-blown release. To do this follow the same steps as above but:
1. Only bump version in `package.json` 1. Add a `-rc.<number>` suffix to the version.
1. use `0.0.0-rc.0` 2. When you publish the release select "pre-release". CI will not automatically
1. When you publish the release, select "pre-release" publish pre-releases.
3. Do not update the chart version or merge in the changelog until the final
release.
#### AUR #### AUR