Repository navigation
[feat] Add leading paragraph "Changes In Settings" to release notes #9742
Description
Current Situation
Often when a new VS Code version is installed, new settings are introduced or existing settings are changed.
It's particularly the changes that, more or less, silently change existing behavior that lead to confusion or loss of privacy.
Sometimes, information about settings changes are burried deep down in the prose of release notes. Recently, this release notes mainly focus on Copilot integration. Users, like me, who don't use AI for programming, are forced to read abundant topics in which they are not interested just to hunt for changes in settings.
Desired Situation
Please add a table to VS Code release notes, listing new settings, deprecated settings and changes in settings (e.g. new default values), like this:
| Setting | Change | Description |
|---|---|---|
| editor.… | New | … |
| workbench.… | Deprecated | … |
| terminal.… | Change | … |
The description should provide information on the behavioral change and the reasoning behind the change.
Activity
Sravan1011 commentedon Aug 12, 2026
Hi — I support adding a “Changes In Settings” summary at the top of each release note. That would make it much easier for users to spot new/changed/deprecated settings without reading all release-note prose.
Proposed template (for the release notes authoring guide or per-release front-matter):
Suggested next step: add this table (with the specific changed settings filled in) as the first subsection of each release note under a heading like “Changes in settings”. I can open a small PR to add a template and update the release-notes authoring doc if that would help. Thoughts?
Sravan1011 commentedon Aug 15, 2026
Nick Trogh (@ntrogh) Axel D. (@SetTrend) ?
SetTrend commentedon Aug 15, 2026
Please, go ahead. Yet, I'm just a user, not a collaborator. So, I cannot tell if your changes will be getting approved.