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

fix: use next version in changelog

This commit is contained in:
Joe Previte 2021-05-12 14:32:20 -07:00
parent 12b1e484be
commit 2438fb307c
No known key found for this signature in database
GPG Key ID: 2C91590C6B742C24
3 changed files with 6 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
.github/PULL_REQUEST_TEMPLATE/release_template.md vendored
View File

@ -12,6 +12,5 @@ Follow "Publishing a release" steps in `ci/README.md`
<!-- Note some of these steps below are redundant since they're listed in the "Publishing a release" docs --> <!-- Note some of these steps below are redundant since they're listed in the "Publishing a release" docs -->
- [ ] double-check github release tag is the commit with artifacts (_note gets messed up after uploading assets_)
- [ ] publish release and merge PR - [ ] publish release and merge PR
- [ ] update the AUR package - [ ] update the AUR package

6
CHANGELOG.md
View File

@ -3,7 +3,7 @@
# Changelog # Changelog
- [Changelog](#changelog) - [Changelog](#changelog)
- [3.11.0](#3110) - [Next Version](#next-version)
- [New Features](#new-features) - [New Features](#new-features)
- [Bug Fixes](#bug-fixes) - [Bug Fixes](#bug-fixes)
- [Documentation](#documentation) - [Documentation](#documentation)
@ -30,7 +30,7 @@ We copy from here into the release notes.
<!-- <!--
Add next version above previous version but below this line using the template Add next version above previous version but below this line using the template
## 0.0.0 ## Next Version
VS Code v0.00.0 VS Code v0.00.0
@ -52,7 +52,7 @@ VS Code v0.00.0
--> -->
## 3.11.0 ## Next Version
VS Code v1.56 VS Code v1.56

7
ci/README.md
View File

@ -24,14 +24,13 @@ Any file or directory in this subdirectory should be documented here.
- It will upload them to the draft release. - It will upload them to the draft release.
6. Run some basic sanity tests on one of the released packages. 6. Run some basic sanity tests on one of the released packages.
- Especially make sure the terminal works fine. - Especially make sure the terminal works fine.
7. Make sure the github release tag is the commit with the artifacts. 7. Publish the release and merge the PR.
8. Publish the release and merge the PR.
1. CI will automatically grab the artifacts and then: 1. CI will automatically grab the artifacts and then:
1. Publish the NPM package from `npm-package`. 1. Publish the NPM package from `npm-package`.
2. Publish the Docker Hub image from `release-images`. 2. Publish the Docker Hub image from `release-images`.
9. Update the AUR package. 8. Update the AUR package.
- Instructions on updating the AUR package are at [cdr/code-server-aur](https://github.com/cdr/code-server-aur). - Instructions on updating the AUR package are at [cdr/code-server-aur](https://github.com/cdr/code-server-aur).
10. Wait for the npm package to be published. 9. Wait for the npm package to be published.
## dev ## dev