docs: 2.3.3 release notes, diagram_theme setting, amber renamed-FK edges - #272
Merged
Conversation
Adds `## Changes in 2.3.3` to whats-new-23.md covering the s3 ambient-credential support, the diagram restyle, the new `display.diagram_theme` setting, the unresolved-node fix, the brace-in-comment and `alter()` fixes, type validation at declaration and insert, the Windows file-store path fix, and PostgreSQL foreign-key indexing. `display.diagram_theme` / `DJ_DIAGRAM_THEME` arrived with the brand-palette work and was documented nowhere; it now has a row in the Display Settings table. The renamed-foreign-key edge changed from `#FF8800` to amber `#C77D3A` in the restyle, and the Computed tier now carries brand orange `#FF5113`. Calling the renamed edge "orange" therefore collided with a tier color, and the notation legend still said "Red=Computed". Both are corrected, and the renamed-edge wording moves to "amber" consistently across read-diagrams, model-relationships, 02-schema-design and the diagram notation spec. Markdown cells only — no notebooks re-executed. The embedded diagram figures were last rendered before the brand palette landed and still show the old colors; regenerating them is tracked by #266.
The page framing still described only the 2.3.0 feature set. Adds the diagram restyle and the ambient-AWS-identity S3 stores to the intro, and gives the diagram work the narrative section every other headline 2.3 feature already had — tier shape and color, the cardinality-only line-weight rule, amber renamed-FK edges, and the display.diagram_theme setting. Also qualifies the upgrade note. "Existing pipelines run identically" is no longer accurate: 2.3.3 rejects a misspelled native type at declaration and raises on a NumPy array inserted into a native blob attribute. Both were already broken rather than working, and the note now says so instead of implying nothing changed.
ttngu207
approved these changes
Sep 9, 2026
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.
Documentation for the 2.3.3 release, being tagged today. Independent of the tag itself — this can land before or after.
What
## Changes in 2.3.3inwhats-new-23.md— a bullet per user-visible change, in the established shape of the 2.3.1 and 2.3.2 sections. The one worth reading closely is the s3 bullet:access_key/secret_keybecoming optional is what unblocks running under an assumed role with no long-lived keys, and it is the reason this release is being cut now.display.diagram_themeinreference/configuration.md— this setting arrived with the brand-palette work in datajoint-python#1544 and was documented nowhere. It takesauto(default),light, ordark, and readsDJ_DIAGRAM_THEME.The renamed-foreign-key edge is amber, not orange. Two things changed in the restyle and the docs tracked neither:
#FF8800— true orange#C77D3A— amber#FF5113— brand orangeSo "orange edges = renamed FK" now names the same color as the Computed tier, and the
read-diagramsnotation legend still saidRed=Computed. Both are wrong and they are wrong in a way that makes the legend self-contradicting. The renamed-edge wording moves to "amber" consistently acrossread-diagrams.ipynb(the section heading and four prose spots),model-relationships.ipynb,02-schema-design.ipynb, and the notation spec inreference/specs/diagram.md, where the entry now carries the hex and says explicitly that it is distinct from the Computed tier above it.Note the many other "orange" mentions in the docs — the domain tutorials,
relational-workflow-model.md, the tier table indiagram.md— were already correct and are untouched. Those refer to Computed ellipses, which really are orange.Scope
Markdown cells only. No notebook was re-executed, so the diff carries no output churn — please confirm that reads true in the notebook diffs.
Known gap, not fixed here: the embedded diagram figures in these notebooks were last rendered 2026-08-13, before datajoint-python#1544 and datajoint-python#1545 landed, so they still show the pre-brand colors. The prose now describes the palette correctly and the pictures do not yet match it. Regenerating them needs a live database and is better done against released 2.3.3 — tracked by #266.
src/llms-full.txtis stale for the same reason (generated 2026-07-17 fromrelease/docs-2.3.1) and can be regenerated byscripts/gen_llms_full.pyin that same pass.mkdocs.yaml'sdatajoint_versiondeliberately stays"2.3"— it marks the minor line, not the patch.Checks
#display-settingsanchor.scripts/check_notebook_versions.pypasses.