Curate Labs Article
GraphForge v0.1.2: Infrastructure Improvements
GraphForge v0.1.2 focused on the professional project infrastructure needed for a graph database to mature in public.
Open Source release
GraphForge is Curate Labs work, released through the DecisionNerd open-source organization. This post is a release note for embedded graph tooling and analytical Python workflows.
GraphForge v0.1.2 was an infrastructure release: documentation, release management, CI automation, and developer experience.
That kind of release is easy to underrate. But for a database-shaped project, a good release process is product work. Users need docs, changelogs, repeatable versioning, and reliable CI before they can trust the query engine itself.
What Shipped
MkDocs Material documentation with GitHub Pages publishing
Installation, quickstart, Cypher language, and API documentation
Versioning, changelog, and automated release checks
PR labeling, component tracking, and release labels
Fixes for integration regressions, unnamed return columns, SKIP/LIMIT behavior, and API docs
Why it matters
This release made GraphForge feel less like a code drop and more like a project people could use, read, and contribute to. That foundation mattered for the release cadence that followed.
Source
GitHub release: GraphForge v0.1.2