Repository navigation
Bump version to 3.13.0 - #850
Conversation
Compile the six changelog.d fragments into CHANGELOG.md [3.13.0] - 2026-10-17 (TWFE weight diagnostics, DML cross-fit fail-closed, deprecation-sentinel copy, CS bootstrap event-study vcov, SC in-space placebo donor pool, SC exact simplex weights) and sync the version string in __init__.py, pyproject.toml, rust/Cargo.toml, llms-full.txt, and CITATION.cff (date-released 2026-10-17). Extend the naming-guard _NEXT_RELEASE map with (3, 13) -> 4.0 so the lifecycle gate re-arms.
Overall Assessment✅ Looks good — no unmitigated P0/P1 findings. Executive Summary
MethodologyNo findings. The affected files do not modify causal methods or assumptions. Relevant Registry entries remain unchanged. Code QualityNo findings. The lifecycle mapping update in PerformanceNo findings. No runtime code paths changed. MaintainabilityNo findings. Version values agree across Tech DebtNo findings. SecurityNo findings. The diff contains no secrets or security-sensitive changes. Documentation/TestsNo findings. Full targeted pytest execution was unavailable because |
Summary
diff_diff/__init__.py,pyproject.toml,rust/Cargo.toml,diff_diff/guides/llms-full.txt, andCITATION.cff(date-released: 2026-10-17).changelog.d/fragments intoCHANGELOG.md[3.13.0] - 2026-10-17and add the comparison link; fragments deleted by the compiler._NEXT_RELEASEintests/test_naming_guard.pywith(3, 13): "4.0"so the version-keyed lifecycle gate re-arms (same step as the 3.12.0 bump, Bump version to 3.12.0 #832).Methodology references (required if estimator / math changes)
Validation
tests/test_naming_guard.py(_NEXT_RELEASEmap entry)tests/test_changelog_fragments.py,tests/test_tracking_files.py,tests/test_docs_ia.py(183 passed);tests/test_naming_guard.pylifecycle-gate test passes with the new entry.Security / privacy
Changelog