Skip to content

Commit c35f927

Browse files
committed
Update release docs
1 parent ffed4b6 commit c35f927

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

docs/releasing.md

+1-2
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
# Releasing (write access required)
22

3-
1. Make sure the needed authentication keys are valid. Most likely the Azure DevOps PAT needs to be regenerated. See below.
43
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:
54
- Making substantial new features available to all users. This can include lifting a feature flag.
65
- Breakage in compatibility with recent versions of the CLI.
@@ -61,7 +60,7 @@
6160

6261
## Secrets and authentication for publishing
6362

64-
Repository administrators, will need to manage the authentication keys for publishing to the VS Code marketplace and Open VSX. Each requires an authentication token.
63+
Repository administrators will need to manage the authentication keys for publishing to the VS Code marketplace and Open VSX. Each requires an authentication token.
6564

6665
To regenerate the Open VSX token:
6766

0 commit comments

Comments
 (0)