Release DocForge 2.0.0
This commit is contained in:
parent
7b21541ab3
commit
3d5fa4e9e8
12 changed files with 86 additions and 37 deletions
|
|
@ -22,13 +22,13 @@ Disposable index and cache schemas may change. Rebuild them rather than copying
|
|||
## Maintained v1.0.0 migration evidence
|
||||
|
||||
`make migration-m5` archives and executes the actual annotated `v1.0.0` release, then opens its
|
||||
fixture, index, and active proposal through DocForge 1.4.0. The frozen tag object is
|
||||
fixture, index, and active proposal through DocForge 2.0.0. The frozen tag object is
|
||||
`2d7d306a37da89f1c860c7f0be161c45386acf61`; it identifies commit
|
||||
`593c173b453236a6872d0a4e88e7a51a67a21cde`.
|
||||
|
||||
The tagged release contains an inherited identity mismatch that the migration proof records
|
||||
rather than hiding: distribution metadata says `1.0.0`, while `docforge.__version__` and the MCP
|
||||
server report `0.15.0`. DocForge 1.4.0 replaces that duplicated state with one authoritative
|
||||
server report `0.15.0`. DocForge 2.0.0 replaces that duplicated state with one authoritative
|
||||
version and requires its package and server values to agree.
|
||||
|
||||
The maintained fixture evidence is exact:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue