docs(changelog): move 0.9.5 features from [Unreleased] into [0.9.5]#435
Merged
Conversation
The 0.9.5 release tag included all of: - Shared MCP daemon (#411) - Per-file staleness banner (#403) - Worktree-borrow detection (#312) - Watcher inotify-budget fix (#276) - Objective-C indexing (#165) - Mixed iOS / React Native / Expo cross-language bridging (#430) But the [0.9.5] block in CHANGELOG.md only had two Fixed entries (the fs-based change detection and default-ignore set), because the major feature entries were still sitting under [Unreleased] when 0.9.5 was tagged. release.yml extracts release notes from the matching version block, so the published v0.9.5 release notes are missing the bulk of what shipped. Move all the [Unreleased] entries that pre-date 0.9.5's tag (commit 318cda1) into [0.9.5], and reset [Unreleased] to empty. The GitHub Release notes for v0.9.5 get updated separately via gh release edit. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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 0.9.5 release tag (
318cda1) included all of:serve --mcpper project across concurrent MCP clients to avoid N× inotify + N× index cost #411)But the
[0.9.5]block in CHANGELOG.md only had two Fixed entries (the fs-based change detection and the default-ignore set), because the major feature entries were still under[Unreleased]when 0.9.5 was tagged.release.ymlextracts notes from the matching version block, so the published v0.9.5 release notes are missing the bulk of what shipped.This PR moves the orphaned
[Unreleased]entries into[0.9.5]and resets[Unreleased]to empty. The on-disk CHANGELOG.md is the source of truth for the release.yml extractor; the GitHub Release notes for v0.9.5 are updated separately viagh release edit(since the release tag is already published, we can't re-run the workflow).Diff is small: 2 inserted lines (the new
## [0.9.5]header line being prepended to the moved content), 4 deleted (the old empty[0.9.5]block with just### Fixedheading + two entries that get re-included in the moved content's Fixed section).🤖 Generated with Claude Code