Repository navigation
docs: Group release-notes.md entries under the release that shipped them - #3428
Closed
it00021hot wants to merge 1 commit into
Closed
it00021hot wants to merge 1 commit into
it00021hot wants to merge 1 commit into
Conversation
The file accumulated every entry under "### 0.7.0 (unreleased)", but v0.7.0 and v0.7.1 have shipped; only the standalone resize_handle entry is still unreleased. Move each entry under the release that first carried it and relabel the pending bucket "Unreleased". Entry text is unchanged; verified against the tagged sources and the GitHub release notes. Prepared with AI assistance.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The root
release-notes.mdaccumulated every entry under a single### 0.7.0 (unreleased)heading, but v0.7.0 (2026-09-28) and v0.7.1 (2026-10-05) have shipped and the heading never moved. Every entry in the section is already released except one, so a reader checking whether an API is still unreleased gets the opposite of the truth.This PR groups the existing entries under the release that first carried them and keeps only genuinely unreleased work under Pending Updates. Entry text is unchanged — only headings were added or moved — verified with a sorted-line diff of before/after.
render_*_layeronRootat the tagSettingGroup::variantcrates/component/src/setting/group.rsatv0.7.0gpui-basecrates/base/src/plot/exists at the tagStrokeStyleabsent,Curvepresent atv0.7.0gpui_base::Rootandgpui_kit::open_windowpub fn open_windowincrates/kit/src/lib.rsat the tagPlotAppearScope)crates/base/src/plot/appear.rsabsent atv0.7.0, present atv0.7.1resize_handlepub fn resize_handleexists only onmain(crates/component/src/resizable.rs); atv0.7.1that file has onlyresize_handle_appearanceNotes:
Unreleasedrather than a guessed version number.TooltipDefaultstooltip: Make show delay and grace period configurable withTooltipDefaults#3376, theDiffviewer diff: Add readonly patch viewer #3378/diff: Add a Git history example and complete review APIs #3388, dialog entrance animations dialog: Support configurable entrance animations #3405). I did not add them, since writing an entry properly needs the PR body per the release-notes command conventions — flagging in case they should be added.Public API
None — documentation-only change.
Prepared with AI assistance; each attribution above was checked against the tagged sources and the GitHub release notes, not inferred from commit dates alone.