Repository navigation
CHANGELOG: splice the 3.11.0 entries merged so far - #6355
Merged
Merged
Conversation
erikdarlingdata
marked this pull request as ready for review
October 21, 2026 21:05
erikdarlingdata
enabled auto-merge (squash)
October 21, 2026 21:05
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.
Claude posting for Erik Darling.
CHANGELOG-only pre-splice for 3.11.0: 19 entries in
[Unreleased]for PRs merged to dev after the entries thatrelease/v3.11.0(#6306) already carries. Only the[Unreleased]section and the link definitions at the foot ofCHANGELOG.mdchanged. No released version and nothing underdocs/changelog/was touched. A new### Changedheading was needed in[Unreleased](it had none); entries are appended within each section, merge order, nothing re-sorted.Scope: what "missing" means here
dev's
[Unreleased]holds only the wave-11 entries (last splice #5932). Most PRs merged since v3.10.0 are already spliced, truth-checked twice, in the[3.11.0]block of #6306 (276 entries). I checked every PR merged since the #5932 splice (216) against #6306'sCHANGELOG.mdanddocs/changelog/3.11.mdby PR number and the issue numbers in its title and entry. Everything up to and including #6307 and #6324 is there. The 19 below are not, so they go to dev's[Unreleased]. When #6306 merges with this PR, the coordinator should expectCHANGELOG.mdanddocs/changelog/3.11.mdto need the usual hand merge; none of my 21 link definitions appears in #6306's file (all new numbers).Source of each entry: the PR body's
CHANGELOG:line where there is one (#6331, #6329, #6327, #6344, #6332, #6328, #6321, #6325, #6319, #6322, #6314, #6316, #6330, #6326), else its "Proposed CHANGELOG line" section (#6308, #6309, #6311, #6313, #6335). TheCHANGELOG:one-liners had no bold headline or issue link, so each was rewritten into the file's- **headline** ([#n]) - bodyform with a link definition at the foot.PR -> section -> entry
Truth checks against the diffs (notes' list)
chart,bucket_minutes;snapshots_only,collection_time) are said to be Darling's, and the entry says Lite's tool is unchanged (both PR bodies say Lite was not changed).get_alert_history; the diff and body show Lite changed too (Lite/Mcp, Lite/Investigations), so the entry says "in Darling and Lite". It also gives the 30-minute window, muted fires counting and the cap at 7.get_overview_baselines, web-only read, not an MCP tool); the entry names which strips get the band and the dots, and that the Overview drops its separate CPU, Memory, Blocked report and Deadlocks charts and File I/O panel.get_procedure_duration_trend'sprocedure_nameis Darling only (the PR body says Lite parity was not done); the entry says so.is_user_processtest), not as a proven fix for the idle-server alert, which the PR says is unconfirmed.[#PR]placeholder, not an issue for this PR.Not truth-checked line by line: #6308, #6309, #6311, #6313, #6335 entries are the PR body's own text (the Proposed CHANGELOG sections), with file lists checked for the product claims (#6309 Darling and Lite files both changed; #6308 Lite; #6311 and #6335 shared collectors).
PRs merged after #6306's coverage with no entry (and why)
CHANGELOG: noneSkipped as the brief says (not merged): #6254/#6342, #6340. #6352, #6301 and #6096 are not merged to dev as of this push (
gh pr viewreturns nothing for them), so nothing to add.Test plan
python -I tools/changelog/changelog_archive.py verify: every version PASS, no FAIL; the one INFO line (5 unreferenced definitions: Lite Overview baseline bands use the server's actual hour under a custom range (#4320) #4325, Size the Linux compose store's workers and work_mem from the product's own formula (#4322) #4400, Hold the raw purge on any hole in the frozen legacy's span, and fill the successor down to raw's floor (#4301) #4401, Charts should show visible flat line at zero instead of empty #85, Deadlock pipeline latency: too many sequential hops before data reaches charts #86) is pre-existing, none of mine.Darling.Tests.exe -class "*Changelog*":Total: 5, Errors: 0, Failed: 0. Build:0 Warning(s),0 Error(s).DARLING_RELEASE_CUT=1 Darling.Tests.exe -method "*StatementCensus_PendingEntries_BlockARelease*": PASSED (Total: 1, Failed: 0). No pending statement-filter entries block the release.