Skip to content

1.0.0 Release Notes (Stable)

Latest
Latest

Choose a tag to compare

View all tags
@ensoriaadmin ensoriaadmin released this 21 Jul 05:46
· 212 commits to main since this release
v1.0.0
b64c0b4

Scope:

  • Publication label: final Stable for tag v1.0.0.
  • Current tagged public release remains v1.0.0-rc.4 until the final tag is
    published.
  • Stable compatibility is limited to normative README.md text,
    fixtures/conformance/v1.0.0/, and the self-contained
    tools/check-conformance-fixtures.mjs.
  • No DocAI HTTP format, authoritative input, conformance contract, checker
    expectation, or projected client behavior changes from reviewed RC.4.

Evidence:

  • The full/compact stable corpus covers resources, workflows, webhooks,
    non-JSON representations, polymorphism, safe retry behavior, and the complete
    unknown / unsupported surface required by README section 9.1.
  • RC4-METADATA-REVIEW.md records focused review completion with no remaining
    stable blocker, wording issue, backlog item, or question.
  • The stable checker validates the corpus in isolation, including focused
    metadata and source-contract negative tests.
  • Existing required-target responses regrade successfully against the reviewed
    contract without new provider submission.
  • OpenAPI comparison evidence remains scoped to the evaluated 0.12.0 fixture,
    target models, task contracts, run dates, and grader policy.

Compatibility:

  • This is the first Stable DocAI HTTP compatibility release.
  • Implementers already targeting v1.0.0-rc.4 require no document-format or
    projected-client migration.
  • Candidate-only evidence paths do not create additional stable promises.
  • Recursive finite representation, public validator APIs, source-to-projection
    validator guarantees, hosted live-provider CI, translations, optional target
    requirements, normalized provider-cost claims, and expanded benchmarks are
    explicitly not promoted by 1.0.0.
  • Later changes must follow README section 3.1 compatibility and versioning
    rules; published tags must not be moved or recreated.

Required pre-tag validation:

  • node docai-http/tools/check-release-readiness.mjs.
  • git diff --check.
  • Confirm the final preparation changes only publication wording, release
    metadata, and review records relative to the reviewed RC.4 contract.
  • Confirm v1.0.0 does not already exist locally or on the release remote.

Publication notes:

  • Create annotated tag v1.0.0 at the reviewed stable-preparation commit.
  • Publish this section as the final release notes.
  • After publication, update current-release wording from v1.0.0-rc.4 to
    v1.0.0 in a separate commit without changing the tag.
Assets 2
Loading