docs(migration): migrate 0.x directly to the latest 2.x (currently 2.3) - #261
Merged
Merged
Conversation
…latest 2.x The migration guide framed the target only as '2.0'. Clarify that a legacy (0.x) pipeline migrates directly to the latest 2.x release (currently 2.3) in a single upgrade — no stepping through 2.0 -> 2.1 -> 2.2 -> 2.3. '2.0' in the guide is the migration surface (type system, codecs, unified stores); 2.1-2.3 build on it with no extra migration steps. Retitle to 'Migrate to DataJoint 2.x' (H1 + nav).
dimitri-yatsenko
added
the
documentation
MilagrosMarin
approved these changes
Aug 17, 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
2 participants
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 migration guide framed the destination only as "2.0", which understated it. This clarifies which versions you migrate to.
Changes
0.x) pipeline migrates directly to the latest 2.x release (currently 2.3) in a single upgrade; there's no need to step through 2.0 → 2.1 → 2.2 → 2.3. (Nav label updated to match.)stores), and that 2.1 (PostgreSQL backend), 2.2 (jobs layer, diagram ops), and 2.3 (upstream/provenance API) build on it with no extra migration steps. Installing the latest release gives you all of them. Reiterates completing the migration while on 2.3 or earlier (thedatajoint.migratehelper is removed in 2.4/2.5).Body "2.0" references are left as-is where they correctly describe the 2.0 feature baseline. No broken anchors (verified nothing links to the old H1 slug).