提交 f896ff39 编写于 作者: T Tomas Vik 提交者: Roman Kuba

New release process

That reflects the automated publishing implemented in !59 and !71
上级 2021425d
# Release process
You need to perform the following steps to release a new version of the extension (examples use `3.0.0` version):
1. Do "sanity check" testing of the extension in your local development. At this stage, you are only making sure that there is no complete failure of the extension.
1. Perform the following two changes:
1. Make sure that the `CHANGELOG.md` contains full information for the release (version, date, changes)([example](https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/blob/master/CHANGELOG.md#v300-2020-06-25)) and commit `git commit -m "Prepare changelog for 3.0.0"`
1. Update the package version in `npm version 3.0.0`
1. `git push origin master` and `git push --tags`
1. Trigger the "publish" step on the tag pipeline.
1. When the extension updates in your VS Code, do another sanity check.
...@@ -88,9 +88,7 @@ Here, the process diverges from the [`gitlab-org/gitlab` security release proces ...@@ -88,9 +88,7 @@ Here, the process diverges from the [`gitlab-org/gitlab` security release proces
### Release the change ### Release the change
- [ ] TODO insert a reference to the release process Follow the [regular release process](release-process.md) to tag a new patch version on the `security-2-2` branch and release it. Patch release for tag `v2.2.0` would have version and tag `v2.2.1`.
Follow the release process to tag a new patch version on the `security-2-2` branch and release it. Patch release for tag `v2.2.0` would have version and tag `v2.2.1`.
Validate that the security issue is fixed in production. Validate that the security issue is fixed in production.
......
### New Release Checklist
- [ ] Update `CHANGELOG.md`
- [ ] Add documentation to README.md about new changes
- [ ] Add community contributors to `CONTRIBUTORS.md` if they are a first time contributor
- [ ] Update version in `package.json`
- [ ] Commit and push release preperation changes
- [ ] Create a tag with the version and push to both GitLab and GitHub
- [ ] Publish extension to marketplace
- [ ] Comment release version and availability to newly released issues
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册