Repository navigation
Release 3.12.0: version, changelog, archive - #6951
Merged
Merged
Conversation
…or lists and platform gates, viewer panels
…o 3.11.0 The ladder gate expects a fixture for the most recent release once the version reads 3.12.0. The upgrade-shape legs build their base from the last shipped release, now 3.11.0.
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.
Claude posting for Erik Darling.
Release 3.12.0, checklist steps 1, 2 and 2a. Draft, not ready.
What is in it
Directory.Build.props:<Version>3.11.0 to 3.12.0 (the only version line).CHANGELOG.md:## [Unreleased]is empty again, and## [3.12.0] - 2026-10-30holds the 3.12.0 index (from the splice of the buffered entries, then compacted bysplit).docs/changelog/3.12.md: the 3.12.0 prose archive.tools/changelog/archive-census.txt: one new row for 3.12.0.Counts
188 index entries in 3.12.0: Important 8, Added 41, Changed 48, Fixed 91. (The buffer held 184 draft files. After merges, drops and additions there are 180 spliced entries plus the 8 Important items I wrote.)
Merges from the drafts
Merged files are archived in
changelog-buffer/archive/2026-10-30-3.12-merged/(not deleted).get_resource_use_by_tag). 6801 archived. PR 6825 had no draft of its own, 6949 already covers V221.web.allowAdminWrites: 6657 absorbed 6745 into one Added entry. A missing key means false (checked inDarlingConfig.AllowAdminWrites, no initializer). 6745 archived. The operator action is in the Important section.Checked against PR bodies
--validate-configwarning.Fixes to the drafts
[#N](url)inline link in the drafts became[#N]with a REF line, because the splice script's marker pattern does not accept the inline form.Important section
Eight items, modelled on 3.11.0's: the V215 to V229 migrations (store schema 214 to 229, no large rewrite, no offline window, what the V219 backfill and V221 builder do after the first start), the Client Timeouts alert turned on by V216 and Lite's one-time marker, Lite's DuckDB schema staying at 78 (read from
DuckDbInitializer.CurrentSchemaVersionat v3.11.0 and dev), theprovision-roles.sqlre-run for self-managed stores (the script changed by 763 lines, issues named), the msdb grants text you supplied (inline code, one line), the token now required on loopback (#6507, #6557),web.allowAdminWritesoff after upgrade, and the stricter server add (port, Windows sign-in over an unverified certificate).Results
changelog_archive.py split,census,verifyandroundtrip: all pass. Verify: 188 index lines for 188 archived entries, 217 distinct[#N]resolve in 3.12.md, CRLF and size ceiling pass, every older archive's hash matches the census. Roundtrip: PROSE INTACT.docs/changelog/3.12.md: 392 hits (3.11.md has 994). Most are the-after a bold title, which is the format. I split the long sentences in the Important section. The remaining long-sentence hits are in the drafted entries.ChangelogIndexAndArchiveTestsandProductVersionDeclarationTests(Darling.Tests built with 0 errors): Total 31, Failed 0, run from the tree with this commit.TheMostRecentRelease_HasALadderFixtureis in a different class and I did not run it. It needs the v3.11.0 ladder fixture, which the other agent pushed to the branch as 544c255 after my run started. No full suite, CI runs it.Other commits on this branch
12b8d2ed4README and docs sync (checklist step 2b): the Darling quick start now usesInstall-Darling.cmdorinstall-darling.ps1, the agent actions list adds module recompile and plan guides, the database protection and Agent alerts collectors are listed, the platform gate table matchesAppliesTo(Agent alerts runs on on-prem servers only), and the tabs page matches the viewer. Every stated count still holds against the code: 48 SQL Server collectors, 29 PostgreSQL collectors, 113 Lite and 276 Darling MCP tools.544c2551bthe v3.11.0 migration ladder fixture (213 rungs, top V214, generated from the v3.11.0 tag) soTheMostRecentRelease_HasALadderFixturepasses once the version is 3.12.0, andDARLING_CURRENT_RELEASEindarling-upgrade-shapes.ymlmoves from 3.10.0 to 3.11.0 (both the 3.11.0 and 3.7.1 Darling zips are still on their releases).MigrationUpgradeLadderLiveTests: Total 9, Failed 0.Step 4 results
DARLING_RELEASE_CUT=1,StatementCensus_PendingEntries_BlockARelease): 0 pending entries, passes.-t:Rebuildof the solution: 0 errors, 1 warning, CA1859 inCollectorRuntimePrecondition.cs, which Clear the CA1859 build warning in JoinWithAnd #6950 fixed on dev after this build ran. This PR's CI builds on top of dev, so it includes the fix.