Release DocForge 2.0.0
This commit is contained in:
parent
7b21541ab3
commit
3d5fa4e9e8
12 changed files with 86 additions and 37 deletions
|
|
@ -5,8 +5,8 @@ people and AI agents can search, inspect, visualize, and change through reviewab
|
|||
Canonical project files remain authoritative. The SQLite graph, previews, rendered manuals, and
|
||||
viewer processes are derived and can be rebuilt.
|
||||
|
||||
This manual describes the DocForge 1.4.0 release. The tagged `v1.0.0` baseline was the first stable
|
||||
product release. Version 1.4.0 preserves its project-scoped graph, CLI and MCP query
|
||||
This manual describes the DocForge 2.0.0 release. The tagged `v1.0.0` baseline was the first stable
|
||||
product release. Version 2.0.0 preserves its project-scoped graph, CLI and MCP query
|
||||
surfaces, hash-approved proposal application, generic and project-owned adapters, declared
|
||||
rendering, and Nodes/Flow/Web model while adding the maintained incremental, projection, adapter
|
||||
SDK, recovery, and release proofs documented below.
|
||||
|
|
@ -132,8 +132,8 @@ python -m docforge.reference_mcp --version
|
|||
python -m docforge.viewer_manager --version
|
||||
```
|
||||
|
||||
For version 1.4.0 these report `docforge 1.4.0`, `docforge-mcp 1.4.0`,
|
||||
`python -m docforge.reference_mcp 1.4.0`, and `docforge-viewer-manager 1.4.0`. Package metadata,
|
||||
For version 2.0.0 these report `docforge 2.0.0`, `docforge-mcp 2.0.0`,
|
||||
`python -m docforge.reference_mcp 2.0.0`, and `docforge-viewer-manager 2.0.0`. Package metadata,
|
||||
Python imports, generated generic and adapter configurations, and these commands share the same
|
||||
version authority.
|
||||
|
||||
|
|
@ -1310,7 +1310,7 @@ make fresh-clone-m5
|
|||
recovery, task-evidence, fresh-wheel, version, artifact, secret-scan, and benchmark suite.
|
||||
`fresh-clone-m5` anonymously clones the exact published candidate over HTTPS, fetches and verifies
|
||||
the frozen annotated `v1.0.0` migration tag, and repeats `release-gate`. Release operators use
|
||||
`make release-pretag` before creating `v1.4.0` and `make release-posttag` after the annotated tag
|
||||
`make release-pretag` before creating `v2.0.0` and `make release-posttag` after the annotated tag
|
||||
points to the exact release commit.
|
||||
|
||||
Project-specific vocabulary, extraction rules, and serialization belong in the project adapter.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue