Document release process
This commit is contained in:
14
ci/README.md
14
ci/README.md
@ -6,6 +6,20 @@ Many of these scripts contain more detailed documentation and options in comment
|
||||
|
||||
Any file and directory added into this tree should be documented here.
|
||||
|
||||
## Publishing a release
|
||||
|
||||
1. Change the version of code-server in `package.json` and push this commit.
|
||||
1. CI will run and generate an NPM package and release packages that you can download
|
||||
as artifacts on Github Actions.
|
||||
1. Create a new draft release with the built release packages.
|
||||
1. Run some basic sanity tests on one of the released packages.
|
||||
1. Publish.
|
||||
1. Download the built npm package and publish it.
|
||||
1. Place the debian releases into `./release-packages` and then push the docker
|
||||
image with `./ci/release-container/push.sh`.
|
||||
1. This will need to be ran on an ARM64 instance as well.
|
||||
1. At some point we need to automate this.
|
||||
|
||||
## dev
|
||||
|
||||
This directory contains scripts used for the development of code-server.
|
||||
|
Reference in New Issue
Block a user