Release notes are unorganized

[bencefr]

Type: Bug

Release notes of VS Code 1.122.0 came with a new format that makes just noise, please format the release notes as before.

VS Code version: Code 1.122.0 (6a49527, 2026-05-27T14:03:01-07:00)
OS version: Darwin arm64 25.5.0
Modes:

[vs-code-engineering]

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.

For Copilot Issues, be sure to visit our Copilot-specific guidelines page for details on the necessary information.

Happy Coding!

[bencefr]

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.

The issue does not fit any category and requires no further information.

[niitinX]

Problem summary:

The readability regression in 1.122 appears to come primarily from changing the release note organization from feature/domain-based grouping to chronological date-based grouping, which reduces scanability and feature discoverability.

Key structural difference

VS Code 1.121

The 1.121 release notes were primarily organized by feature/domain categories such as:

• Agents
• Language Models
• Integrated Browser
• Terminal
• Languages
• Editor

This structure helped users:

• quickly scan for areas relevant to them
• mentally group related changes
• skip sections they were not interested in
• discover major features more easily

The release notes also contained:

• screenshots
• diagrams
• feature summaries
• descriptive section headers
• visual spacing between major topics

These acted as visual anchors and improved navigation while scrolling.

---

VS Code 1.122

The 1.122 release notes are primarily organized chronologically by date:

• May 23, 2026
• May 22, 2026
• May 21, 2026
• etc.

This format feels closer to a chronological changelog stream than the feature-oriented release documentation used in @1.121.

As a result:

• feature discoverability becomes harder
• users cannot quickly scan by area/functionality
• unrelated features are mixed together

The chronological format may help support faster incremental publishing, but it also appears to reduce scanability for users looking for updates by functionality.

---

Final thoughts

The issue does not appear to be caused by the amount of content, but rather by how the content is grouped and visually prioritized.

The 1.121 format felt easier to scan because it aligned with how users mentally categorize VS Code functionality.

The 1.122 format is more chronological and implementation-oriented, which reduces readability and feature discoverability for end users.

I’ve attached screenshots comparing both versions for reference.

[dmitrivMS]

Those look like Insiders release notes, not Stable.

[dmitrivMS]

Just installed 1.122 fresh, it looks correct:

[ntrogh]

The 1.122 release accidentally went out before the release notes were published to the website. In that case, VS Code pulls down the latest version of the Insiders release notes to give you at least some indication of what's new.

The release notes are cached for a bit but should eventually pull the latest notes. Also available on the website: https://code.visualstudio.com/updates/v1_122