Skip to content

docs(whats-new-23): add 2.3.1 cascade fix bullet; refresh releases link #212

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MilagrosMarin merged 3 commits into from
Jul 17, 2026
Merged

docs(whats-new-23): add 2.3.1 cascade fix bullet; refresh releases link #212

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
74e7cd9
docs(whats-new-23): add 2.3.1 cascade fix bullet; refresh releases link
MilagrosMarin Jul 17, 2026
07f3818
docs(whats-new-23): drop ValueError callout per review
MilagrosMarin Jul 17, 2026
9b4a903
docs(whats-new-23): generalize release-notes link to cover the 2.3.x …
MilagrosMarin Jul 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion src/about/whats-new-23.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,7 @@ DataJoint 2.3 adds a first-class **upstream read surface** — `Diagram.trace` a

- **`strict_provenance` removed.** The opt-in `dj.config["strict_provenance"]` runtime guardrail that shipped in 2.3.0 has been retired. Comprehensively checking the `make()` read/write contract across every access path is a code-inspection problem rather than a runtime one, so it is validated at review or deploy time rather than by an in-process flag. The flag was off by default with no known adoption, so existing pipelines are unaffected. The ergonomic read surface — `Diagram.trace` and `self.upstream` — is unchanged, and the rules are documented as the [make() reproducibility contract](../reference/specs/autopopulate.md#43-the-make-reproducibility-contract).
- **Python 3.14 support.** `requires-python` now spans `>=3.10,<3.15`; CI exercises both ends of the range (3.10 and 3.14).
- **Cascade multi-part-master fix.** `Table.delete(part_integrity="cascade")` now restricts the master from *every* restricted Part, closing a silent-integrity path where two Parts of the same Master reached through different foreign-key paths could leave the Master with rows that should have been deleted. See [Cascade Specification](../reference/specs/cascade.md).
- **Garbage-collection fix.** `gc.collect()` now discovers codec-referenced files correctly, closing a path where live custom-codec and schema-addressed object-store files (`<object@>`, `<npy@>`) could be misclassified as orphans and deleted. See [Clean Up Object Storage](../how-to/garbage-collection.md).

## Overview
Expand Down Expand Up @@ -105,4 +106,4 @@ It is PostgreSQL-only (raising a clear error on other backends), idempotent at t
- [Deployment Operations](../reference/specs/deploy-operations.md) — the `dj.deploy` module
- [Cascade Specification](../reference/specs/cascade.md) — propagation rules shared with `trace`
- [What's New in 2.2](whats-new-22.md) — Previous release
- [Release Notes (v2.3.0)](https://github.com/datajoint/datajoint-python/releases) — GitHub changelog
- [Release Notes (2.3.x)](https://github.com/datajoint/datajoint-python/releases) — GitHub changelog
Loading