Microsoft/vscode
1
0
Fork 0
mirror of https://github.com/microsoft/vscode.git synced 2026-04-17 15:24:40 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update proposed API versioning instructions (#293291)

Browse Source
This commit is contained in:
Harald Kirschner
2026-02-21 21:03:57 -08:00
committed by GitHub
parent 6c1efa9aaf
commit c760ee7f43
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.github/instructions/api-version.instructions.md vendored
View File

@@ -11,7 +11,7 @@ When a proposed API is changed in a non-backwards-compatible way, the version nu
// version: 1
```
No semver, just a basic incrementing integer. The corresponding version number in the extension's package.json must be incremented to match (you could remind the user of this if you don't have access to the extension code yourself).
No semver, just a basic incrementing integer. See existing examples in `vscode.proposed.chatParticipantPrivate.d.ts` (version 12), `vscode.proposed.chatProvider.d.ts` (version 4), and other chat/languageModel proposals. The corresponding version number in the extension's package.json must be incremented to match (you could remind the user of this if you don't have access to the extension code yourself).
An example of a non-backwards-compatible change is removing a non-optional property or changing the type to one that is incompatible with the previous type.