Repository navigation
changelog: the four missing fragments from the pre-check window - #4048
Closed
sethkarten wants to merge 2 commits into
Closed
sethkarten wants to merge 2 commits into
sethkarten wants to merge 2 commits into
Conversation
Contributor
Author
|
The five catchup fragments now ride the release PR #4047 directly (per Seth's release-shape directive): the fragment commits cherry-picked onto release/v0.10.3 at 285a609 and folded into its CHANGELOG 0.10.3 section (the #3858 test-only raw line cut per the crabbox review). This PR's content is carried; closing as superseded. |
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
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.
Motivation
The v0.10.3 fragment audit found four merged PRs (all from the 2026-10-29/30 window, before #3790 restored the changelog-fragment check) that changed shipped paths without a
.changes/fragment and without theno-changeloglabel:agent_observe.recent_messagesreads its message membersMethod
One fragment per missing PR, written in the existing fragments' tone (one user-facing line each). Thirteen other fragment-less merges are exempt by convention (the
no-changeloglabel: the test/build batch #3874-#3880/#4006/#3868/#3844, the docs PR #4021, the TS-removal #3870, the bugbot-flags PR #3817).Validation
The fragments fold via the standard
fold_changelog.pycontract (make fold-gates); the catchup rides the queue so the release re-dispatch folds them into the v0.10.3 section.Note
Low Risk
Changelog-only additions with no shipped code or config changes.
Overview
Adds five one-line
.changes/fragments so merged user-facing fixes can fold into the next release viafold_changelog.py.The new bullets document:
agent_observe.recent_messagesreading real message members; live timers on running tool calls; MCP config limited to user settings (not cloned project declarations at session start); Python card clicks opening the card’s own session; and Windows multi-line paste arriving as a single event again.No runtime or workflow logic is modified—only the fragment files named in the PR description.
Reviewed by Cursor Bugbot for commit d04672a. Bugbot is set up for automated code reviews on this repo. Configure here.
Note
Add four missing changelog fragments from the pre-check window
Backfills change notes that were missing from the pre-check window. Each note is a separate file under
.changes/:agent_observe.recent_messagesreads message members instead of inferring them from previewsAlso adds live-tool-call-timer.md: tool calls show a live timer while running.
Macroscope summarized d04672a.