docs(changelog): backfill 3.1.0, 3.0.0, 2.0.2 entries - #310
Merged
Conversation
The changelog had drifted -- the last entry was 2.0.1, while 2.0.2, the entire 3.0.0 modernization, and the 3.1.0 line had all shipped with their notes living only in commits, PRs, and GitHub Releases. Consolidate them into CHANGELOG.md, newest-first, in the existing Keep a Changelog format: - [3.1.0] - 2026-07-09: NumPy interop (#306), UI quality-of-life (#293-#305), ZeroDimConfig.recall (#308), prebuilt CI deps (#282), docs-store Pages (#291,#292) - [3.0.0] - 2026-07-07: reworked from the v3.0.0 release notes (~70 PRs, #238) - [2.0.2] - 2026-05-22: the missing packaging/CI maintenance entry This also fixes the release-notes automation: publish.yml's github-release job extracts the top CHANGELOG block, which was stale [2.0.1]; the final v3.1.0 tag will now emit the correct [3.1.0] notes.
Merged
ofloveandhate
added a commit
that referenced
this pull request
Jul 9, 2026
Promote the release candidate to the **final 3.1.0**: `VERSION` `3.1.0rc1` → `3.1.0`. Once merged, tag `v3.1.0` on the develop tip. That routes through `publish.yml`'s final-release path (`is_prerelease=false`): real **PyPI** publish, Sigstore-signed **GitHub Release** (notes from the now-current `[3.1.0]` CHANGELOG block, #310), and **versioned docs** deploy — plus the extra `check_timing_freshness` gate that only final releases run. `VERSION` is in the workflows' `paths-ignore`, so this PR runs no CI and needs no approvals.
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.
The changelog had drifted badly: the last entry was 2.0.1, while 2.0.2, the entire
3.0.0 modernization, and the 3.1.0 line had all shipped — with their notes living only
in commit messages, PRs, and GitHub Releases. This consolidates them back into
CHANGELOG.md,newest-first, in the existing Keep a Changelog format.
New entries
quality-of-life batch (TypeError when getting the variable group of a system. #293–add
is_distinct_up_to#304, feat: UI quality-of-life batch (#293–#304) + solution group projection — 3.1.0.dev1 #305),ZeroDimConfig.recall(feat(records): ZeroDimConfig.recall — force a fresh re-track past the records recall #308), prebuilt CI deps(ADR-0049, docs: prebuilt CI deps — ADR-0049 + CLAUDE.md refresh #282), and docs-store Pages (ADR-0050, 3.0.0 versioned-docs deploy skipped (deploy_docs job's is_release gate) #291, docs: serve Pages from docs-store branch; fix #291 versioned-docs deploy #292).
themed index in CLI, so many bugfixes, block structured systems, mhom exposed, user homotopy, two-level parallelism... #238) into Added / Changed / Fixed sections.
Older 1.0.x / 2.0.1 entries and the commented template are untouched.
Why now (load-bearing)
publish.yml'sgithub-releasejob builds the release body from the topCHANGELOG.mdblock. That block was the stale [2.0.1] — so a final
v3.1.0tag would have published 2.0.1'snotes as the 3.1.0 release. With this merged, the extraction yields exactly the [3.1.0] block
(verified locally against the workflow's extraction logic).
Docs-only (
**/*.md→paths-ignore), so this runs no CI. Merge before taggingv3.1.0.