Skip to content

[pull] main from microsoft:main #958

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pull merged 5 commits into from
Feb 22, 2026
Merged

[pull] main from microsoft:main #958

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
c760ee7
Update proposed API versioning instructions (#293291)
digitarald Feb 22, 2026
8494e45
Allow ghostty terminal from external terminal osx, linux (#286983)
anthonykim1 Feb 22, 2026
303416b
debt - check in stale lock file for packages (#296797)
bpasero Feb 22, 2026
c98021a
sessions - support always on top for floating windows (#296796)
bpasero Feb 22, 2026
718b93c
style - reduce focus outline for a more modern look (#296799)
bpasero Feb 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/instructions/api-version.instructions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
Loading
Loading