Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
布及
code-server
提交
82073743
C
code-server
项目概览
布及
/
code-server
与 Fork 源项目一致
从无法访问的项目Fork
通知
1
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
C
code-server
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
未验证
提交
82073743
编写于
2月 07, 2023
作者:
A
Asher
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Update release guide
上级
71ff747c
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
18 addition
and
14 deletion
+18
-14
docs/MAINTAINING.md
docs/MAINTAINING.md
+18
-14
未找到文件。
docs/MAINTAINING.md
浏览文件 @
82073743
...
...
@@ -142,24 +142,28 @@ changelog](https://github.com/emacs-mirror/emacs/blob/master/etc/NEWS).
### Publishing a release
1.
Go to GitHub Actions > Draft release > Run workflow off commit you want to
release. CI will automatically upload the artifacts to the release. Make sure CI
has finished on that commit.
1.
CI will automatically grab the
artifacts, publish the NPM package from
`npm-package`
, and publish the Docker
Hub image from
`release-images`
.
1.
Publish release.
1.
After, create a new branch called
`release/v0.0.0`
(replace 0s with actual version aka v4.5.0)
1.
Summarize the major changes in the
`CHANGELOG.md`
1.
Bump chart version in
`Chart.yaml`
.
1.
Go to GitHub Actions > Draft release > Run workflow on the commit you want to
release. Make sure CI has finished the build workflow on that commit or this
will fail.
2.
CI will automatically grab the build artifact on that commit, inject the
version into the
`package.json`
, put together platform-specific packages, and
upload those packages to a draft release.
3.
Summarize the major changes in the
`CHANGELOG.md`
.
4.
Copy the relevant changelog section to the release then publish it.
5.
CI will automatically publish the NPM package, Docker image, and update
Homebrew using the published release assets.
6.
Bump the chart version in
`Chart.yaml`
and merge in the changelog updates.
#### 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.
use
`0.0.0-rc.0`
1.
When you publish the release, select "pre-release"
1.
Add a
`-rc.<number>`
suffix to the version.
2.
When you publish the release select "pre-release". CI will not automatically
publish pre-releases.
3.
Do not update the chart version or merge in the changelog until the final
release.
#### AUR
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录