docs: remove "Publishing A Release" from ci/README.md

Deleted "Publishing A Release" section from the readme.md file in the 'ci'
folder and then pasting the section in 'Maintaining.md'
This commit is contained in:
Prashant168 2021-05-25 20:13:52 +05:30 committed by Joe Previte
parent e02ecc2c80
commit 7dfd3676c1
No known key found for this signature in database
GPG Key ID: 2C91590C6B742C24

View File

@ -10,27 +10,6 @@ Any file or directory in this subdirectory should be documented here.
- [./ci/lib.sh](./lib.sh) - [./ci/lib.sh](./lib.sh)
- Contains code duplicated across these scripts. - Contains code duplicated across these scripts.
## Publishing a release
1. Run `yarn release:prep` and type in the new version i.e. 3.8.1
2. GitHub actions will generate the `npm-package`, `release-packages` and `release-images` artifacts.
1. You do not have to wait for these.
3. Run `yarn release:github-draft` to create a GitHub draft release from the template with
the updated version.
1. Summarize the major changes in the release notes and link to the relevant issues.
2. Change the @ to target the version branch. Example: `v3.9.0 @ Target: v3.9.0`
4. Wait for the artifacts in step 2 to build.
5. Run `yarn release:github-assets` to download the `release-packages` artifact.
- It will upload them to the draft release.
6. Run some basic sanity tests on one of the released packages.
- Especially make sure the terminal works fine.
7. Publish the release and merge the PR.
1. CI will automatically grab the artifacts and then:
1. Publish the NPM package from `npm-package`.
2. Publish the Docker Hub image from `release-images`.
8. Update the AUR package.
- Instructions on updating the AUR package are at [cdr/code-server-aur](https://github.com/cdr/code-server-aur).
9. Wait for the npm package to be published.
## dev ## dev