You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Docs release step for the 2.3 line, gated on an installable datajoint==2.3.x and a live database — so it happens at/around tag time, not in a normal content PR.
What & why
mkdocs.yaml has datajoint_version: "2.2" (line ~253), but all 22 tutorial/how-to notebooks currently show DataJoint 2.2.2 connected banners, so it's consistent today and CI is green. To advance the covered version to 2.3, the notebooks must be re-executed under 2.3.x (so their banners read 2.3.x) and the marker bumped — together.
scripts/check_notebook_versions.py compares each notebook's connection banner against extra.datajoint_version, matching major.minor (any patch within the line passes). .github/workflows/check-notebooks.yml runs this guard on every PR touching notebooks / mkdocs.yaml / the script. No workflow executes notebooks — re-execution is manual.
The recipe (one atomic PR)
Install the released datajoint==2.3.x (2.3.0 or 2.3.1 both satisfy a "2.3" marker).
Stand up a live database — the banner is printed on connection, so notebooks must actually connect and execute (postgres/mysql).
Re-execute all 22 notebooks under src/tutorials/** and src/how-to/** so their committed banners read 2.3.x.
Activity
docs(release): re-execute notebooks under DataJoint 2.3.1; bump dataj…
docs(release): re-execute notebooks under DataJoint 2.3.1; bump dataj…