Merge pull request #3906 from github/koesie10/update-release-docs
Update release docs
This commit is contained in:
@@ -1,6 +1,5 @@
|
|||||||
# Releasing (write access required)
|
# Releasing (write access required)
|
||||||
|
|
||||||
1. Make sure the needed authentication keys are valid. Most likely the Azure DevOps PAT needs to be regenerated. See below.
|
|
||||||
1. Determine the new version number. We default to increasing the patch version number, but make our own judgement about whether a change is big enough to warrant a minor version bump. Common reasons for a minor bump could include:
|
1. Determine the new version number. We default to increasing the patch version number, but make our own judgement about whether a change is big enough to warrant a minor version bump. Common reasons for a minor bump could include:
|
||||||
- Making substantial new features available to all users. This can include lifting a feature flag.
|
- Making substantial new features available to all users. This can include lifting a feature flag.
|
||||||
- Breakage in compatibility with recent versions of the CLI.
|
- Breakage in compatibility with recent versions of the CLI.
|
||||||
@@ -61,7 +60,7 @@
|
|||||||
|
|
||||||
## Secrets and authentication for publishing
|
## Secrets and authentication for publishing
|
||||||
|
|
||||||
Repository administrators, will need to manage the authentication keys for publishing to the VS Code marketplace and Open VSX. Each requires an authentication token.
|
Repository administrators will need to manage the authentication keys for publishing to the VS Code marketplace and Open VSX. Each requires an authentication token.
|
||||||
|
|
||||||
To regenerate the Open VSX token:
|
To regenerate the Open VSX token:
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user