Changeset version bump

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

[email protected]

Patch Changes

• • Fix: Remove request content from UI messages to improve performance and reduce clutter (Extension Gray/Blank Screen Issue - Consolidated Investigation & Current Status #5601 by @MuriloFP, [BUG] Grey screen - Restarted VSCode and after the compaction of the context window is not working #8594 by @multivac2x, [BUG] read_file contents persisted in ui_messages.json cause bloat/gray screen #8690 by @hannesrudolph, PR by @mrubens)

[roomote]

Review Summary

I've reviewed this changeset version bump PR. The previously identified issue has been resolved.

Issues Found

• Incomplete CHANGELOG entry: The CHANGELOG for version 3.28.18 only includes 1 of the 5 changes that were in the deleted changeset file (.changeset/v3.28.18.md). The missing changes are: RESOLVED - The CHANGELOG has been updated to include all 5 changes from the consumed changeset:
  • Fix: Remove request content from UI messages to improve performance and reduce clutter
  • Fix: Prevent file editing issues when git diff views are open
  • Fix: Add userAgent to Bedrock client for version tracking
  • Feat: Z AI now uses only two coding endpoints for better performance
  • Feat: Update image generation model selection for improved quality

All changes from the consumed changeset are now properly documented in the CHANGELOG.

[roomote]

The CHANGELOG entry for 3.28.18 is incomplete. The changeset file that was deleted contained 5 distinct changes (fixes for file editing with git diff views, userAgent for Bedrock, Z AI endpoint optimization, and image generation model updates), but only the first change about removing request content from UI messages appears in the CHANGELOG. This means users checking the CHANGELOG will not see 4 of the 5 changes included in this release. The CHANGELOG should be updated to include all changes from the consumed changeset, or the changeset file format needs to be corrected to ensure all items are properly extracted.