@@ -137,43 +137,19 @@ changelog](https://github.com/emacs-mirror/emacs/blob/master/etc/NEWS).
137
137
138
138
## Releases
139
139
140
- With each release, we rotate the role of release manager to ensure every
141
- maintainer goes through the process. This helps us keep documentation up-to-date
142
- and encourages us to continually review and improve the flow.
143
-
144
- If you're the current release manager, follow these steps:
145
-
146
- 1 . Create a [ release issue] ( ../.github/ISSUE_TEMPLATE/release.md )
147
- 1 . Fill out checklist
148
- 1 . Publish the release
149
- 1 . After release is published, close release milestone
150
-
151
140
### Publishing a release
152
141
153
142
1 . Create a new branch called ` release/v0.0.0 ` (replace 0s with actual version aka v4.5.0)
154
143
1 . If you don't do this, the ` npm-brew ` GitHub workflow will fail. It looks for the release artifacts under the branch pattern.
155
- 1 . Run ` yarn release:prep ` and type in the new version (e.g., ` 3.8.1 ` )
156
- 1 . GitHub Actions will generate the ` npm-package ` , ` release-packages ` and
157
- ` release-images ` artifacts. You do not have to wait for this step to complete
158
- before proceeding.
159
- 1 . Run ` yarn release:github-draft ` to create a GitHub draft release from the
160
- template with the updated version. Make sure to update the ` CHANGELOG.md ` .
144
+ 1 . Run ` yarn release:prep <version> ` (e.g., ` yarn release:prep 3.8.1 ` )
161
145
1 . Bump chart version in ` Chart.yaml ` .
162
- 1 . Summarize the major changes in the release notes and link to the relevant
163
- issues.
164
- 1 . Change the @ to target the version branch. Example: ` v3.9.0 @ Target: release/v3.9.0 `
165
- 1 . Wait for the ` npm-package ` , ` release-packages ` and ` release-images ` artifacts
166
- to build.
167
- 1 . Run ` yarn release:github-assets ` to download the ` release-packages ` artifact.
168
- They will upload them to the draft release.
169
- 1 . Run some basic sanity tests on one of the released packages (pay special
170
- attention to making sure the terminal works).
171
- 1 . Publish the release and merge the PR. CI will automatically grab the
146
+ 1 . Summarize the major changes in the ` CHANGELOG.md `
147
+ 1 . Download CI artifacts and make sure code-server works locally.
148
+ 1 . Merge PR and wait for CI build on ` main ` to finish.
149
+ 1 . Go to GitHub Actions > Draft release > Run workflow off ` main ` . CI will automatically upload the artifacts to the release.
150
+ 1 . Add the release notes from the ` CHANGELOG.md ` and publish release. CI will automatically grab the
172
151
artifacts, publish the NPM package from ` npm-package ` , and publish the Docker
173
152
Hub image from ` release-images ` .
174
- 1 . Update the AUR package. Instructions for updating the AUR package are at
175
- [ coder/code-server-aur] ( https://github.com/coder/code-server-aur ) .
176
- 1 . Wait for the npm package to be published.
177
153
178
154
#### AUR
179
155
0 commit comments