Splice the pending CHANGELOG entries merged through 2026-09-26T17:37:33Z UTC - #4440
Merged
Merged
Conversation
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.
Moves the CHANGELOG entries carried in merged PR descriptions into
[Unreleased]. Cut: PRs merged at or before 2026-09-26T17:37:33Z UTC; the next splice starts after it.What changes
One Python script (not committed, run under
/tmp) read a pre-fetched JSONL of 150 merged pull requests (all merged after 2026-09-25T07:08:52Z, the last timeCHANGELOG.mdwas touched before this window, and at or before the cut) and mechanically spliced each PR's## CHANGELOG entrysection into[Unreleased].Spliced: 128 PRs total.
Each entry was inserted at the top of its section's list (newest PR number first), matching the file's own existing order. Each entry's
REF:definition was appended to the file's trailing definitions block, skipped when the label already existed there.Section choices (no
SECTION:line in the PR body)Three PRs carried a real ENTRY/REF block with no
SECTION:header. Assigned by reading each PR's own diff:Mechanical fixes
[#4198]: .../pull/4198REF, inconsistent with the label's first-seen form (.../issues/4198, from MCP budget: get_plan_corrections defaults sized to the shared response budget (#4198) #4257/MCP budget: add get_collection_log per-server response budget and error_message preview (#4198) #4265/MCP budget: describe_custom_view_catalog groups measures by source, under the response budget (#4198) #4272/MCP budget: get_query_store_top's default stays under 32 KB (#4198) #4273). MCP read tools have no default response-size budget: at default arguments 12 tools return >50 KB and 3 return >100 KB for one server, more than an agent client's per-result cap #4198 is a GitHub issue, not a pull request, so the issues-form was kept for every occurrence of that label.[#4203]: https://github.com/erikdarlingdata/PerformanceMonitor/pull/4360— a REF labeled for issue Web /api/read/* handlers never thread RequestAborted into the underlying store query #4203 but pointing at PR Thread cancellation through 7 Blocking web reads (#4203) #4360's own pull URL. Web /api/read/* handlers never thread RequestAborted into the underlying store query #4203 is a GitHub issue, so the URL was corrected to.../issues/4203.Skips (22 PRs — no user-visible entry)
SECTION: Noneor opens with free-text "None…" (test-only changes, refactors, or entries deferred to a not-yet-merged parent PR): CI: distinct-chunk counting for job_history's two-scan floor proof (flake from #4235) #4275, MCP budget: finish get_analysis_findings default limit and text previews (#4198) #4266, A budget pin over every MCP read tool (part of #4198) #4224, Pin Lite's MCP read tools under the #4198 response budget (#4198) #4290, lane-orders: lanes skip the plain-English pass on PR bodies #4314, A live test holds #4247's readers under half their deadlines without the dropped indexes (#4247) #4318, Make the PgTarget anomaly and blocking tests independent of the wall clock (#4274) #4323, Derive each raw hypertable's chunk interval from ingest (#4211) #4332, Flaky test: the failure-facts reader always reads once before checking the writers (#4312) #4335, Payload-dimension pre-filter test no longer asserts a cluster-wide WAL delta (#4354) #4356, Cover the MCP Query Store regression reader's baseline lower bound in the census guard (#4310) #4375, Move plan-force audit sanitizer into the shared row mapper (#4376) #4377, Anchor the Lite CPU-spike scenario to a UTC-day boundary #4385, Pin that a literal end before applied_through reads raw on the grid and MCP (#3953) #4381, Make two live tests independent of the extension and the wall clock (#3953) #4389, Open fresh connections after the upgrade test restarts its server #4397, Measure the DuckDB memory trim by the memory it releases #4398, Split AlertNotebookEndpoint's authored templates into per-family files (#4223) #4410, Retry the DuckDB trim test when a parallel test holds the trim lock #4415, Top-N raw reads apply the hourly rollups' zero-interval filter, so both tiers agree by construction (#4394) #4414, Add authored-notebook context plumbing (#4223) #4425, Add the missing [Unreleased] CHANGELOG entries for eleven merged PRs #4438. Each was re-checked directly against the PR's raw body for an indented## CHANGELOG entryblock the parser could have missed; none had one — every one of the 22 either has noCHANGELOG entryheading at all or an unindentedNone/test-only line.No PR number in this input window's
[#N]labels already appeared in[Unreleased], so rule 2's skip-if-already-present case did not apply to any entry.#4206 / #4208 handling
[Unreleased]did not already carry it before this splice.## CHANGELOG entryblock was indented four spaces in its PR body (a Markdown code block), which the splice parser did not read as a section heading, so it was wrongly treated as a skip. It is now spliced from that body: twoFixedbullets, plus one sentence added to the first bullet from the diff (git show 731512799 --stat,PgMigrations.cs) naming the store schema rung the fix depends on — V143, thecollect.query_store_interval_latesttable.Self-check
Every
[#N]cited in an[Unreleased]bullet has exactly one[#N]:definition in the file, and no duplicate label definitions exist anywhere in the file (checked programmatically after the splice). File stays LF-only (verified: the committed blob was already LF-only despite the repo'seol=crlfcheckout attribute; converted CHANGELOG.md's working-tree CRLFs to LF before editing, matching the committed history).Diff is exactly
CHANGELOG.md.Test plan
Built
Darling/Darling.Tests/Darling.Tests.csproj(Release,EnableWindowsTargeting=true), 0 errors. Ran the realDarling.Tests.dllin-process (Microsoft.WindowsDesktop.Appframework entry stripped from its runtimeconfig, the rest of the recipe unchanged).origin/devhad not moved past this branch's base (2c34fc0b0), so no merge was needed before the run.ChangelogIndexAndArchiveTests: 5/5 passed on 3d3d62d6 merged with dev 2c34fc0b0CHANGELOG entry
SECTION: None — this PR is the CHANGELOG change itself.