Versioning Graph Diagrams
Track changes to graph diagrams with snapshot versioning and lifecycle tagging. Create named snapshots, compare versions, and manage entity lifecycles with active, planned, and deprecated states.
Graph diagrams support version history, allowing you to track changes over time, create named snapshots, and restore previous states. Combined with lifecycle tagging, you can manage entity evolution by marking nodes as active, planned, or deprecated.
Version Storage
Graph diagram versions are stored in the same JSON file as the main diagram:
What Gets Versioned
Version snapshots capture the complete diagram state:
Creating a Version
Lifecycle Tagging on Graph Nodes
Individual nodes in a graph diagram can carry lifecycle status, providing a visual overlay of architectural intent.
Lifecycle status propagates to derived views. An entity marked as deprecated in the graph diagram appears as deprecated in ERD views, graph views, and search views automatically.
Succession Edges
When deprecating a node, assign its replacement using the replaced-by field. This creates traceable succession:
Version Metadata
Each version includes:
Viewing Version History
The History panel shows all versions in chronological order with the most recent at the top.
Restoring a Version
Comparing Versions
You can compare any two versions to see what changed:
Change Detection
The versioning system detects changes at multiple levels:
Version Naming Conventions
Use descriptive names that indicate what changed:
Versioning vs Lifecycle Tagging
These two features serve different purposes and work together: