Skip to content

Release 3.12.0: version, changelog, archive - #6951

Merged
erikdarlingdata merged 3 commits into
devfrom
release/v3.12.0
Oct 30, 2026
Merged

erikdarlingdata merged 3 commits into
devfrom
release/v3.12.0

Conversation

@erikdarlingdata

@erikdarlingdata erikdarlingdata commented Oct 30, 2026 •

Copy link
Copy Markdown
Owner

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-30 holds the 3.12.0 index (from the splice of the buffered entries, then compacted by split).
  • 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).

Checked against PR bodies

  • 6536: the draft only said anomaly. The PR maps anomaly, cpu, memory, io and disk to resources and jobs to jobs. Fixed, plus the in-flight request note.
  • 6509: extended as above. 6508 and 6556 were accurate, and 6556 gained the agent_id check, the per-role instructions and the --validate-config warning.

Fixes to the drafts

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.CurrentSchemaVersion at v3.11.0 and dev), the provision-roles.sql re-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.allowAdminWrites off after upgrade, and the stricter server add (port, Windows sign-in over an unverified certificate).

Results

  • changelog_archive.py split, census, verify and roundtrip: 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.
  • Plain-English checker on 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.
  • ChangelogIndexAndArchiveTests and ProductVersionDeclarationTests (Darling.Tests built with 0 errors): Total 31, Failed 0, run from the tree with this commit. TheMostRecentRelease_HasALadderFixture is 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

  • 12b8d2ed4 README and docs sync (checklist step 2b): the Darling quick start now uses Install-Darling.cmd or install-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 matches AppliesTo (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.
  • 544c2551b the v3.11.0 migration ladder fixture (213 rungs, top V214, generated from the v3.11.0 tag) so TheMostRecentRelease_HasALadderFixture passes once the version is 3.12.0, and DARLING_CURRENT_RELEASE in darling-upgrade-shapes.yml moves 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

  • Statement census release gate (DARLING_RELEASE_CUT=1, StatementCensus_PendingEntries_BlockARelease): 0 pending entries, passes.
  • Full -t:Rebuild of the solution: 0 errors, 1 warning, CA1859 in CollectorRuntimePrecondition.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.

…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.
@erikdarlingdata
erikdarlingdata marked this pull request as ready for review October 30, 2026 12:39
@erikdarlingdata
erikdarlingdata merged commit bd3adab into dev Oct 30, 2026
34 of 36 checks passed
@erikdarlingdata
erikdarlingdata deleted the release/v3.12.0 branch October 30, 2026 13:03
@erikdarlingdata erikdarlingdata mentioned this pull request Oct 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant