Skip to content

Releases

lintel-api 0.1.0a7

lintel-api 0.1.0a7 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 12 Nov 01:44
0e8d012
  • Adds JSON:API reads and named command and observation routes for the bounded
    Batten task-board profile. Both use the admitted prepared API v5 and the same
    Batten execution scopes as GraphQL.
  • Generates OpenAPI 3.1 and named operation descriptions for forward paging,
    resource refetch, one-hop assignee expansion, and declared commands.
  • Qualifies the local task-board profile on one Batten host with PostgreSQL 18.6
    and Chromium, including exact Decimal values, actor switching, command
    confirmation, and recovery after a lost response. Existing Relay clients can
    continue using GraphQL.

lintel-api 0.1.0a6

lintel-api 0.1.0a6 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 12 Nov 00:46
2163327

First release that goes from a UMF document to a served GraphQL API.
Versions 0.1.0a2 to 0.1.0a5 were never published; their changes ship here.

  • lintel example | prepare | serve command line and an in-memory execution port
    (lintel.memory), lintel.trust.pin_for, lintel.app.
  • The prepared-API build tool, previously the never-published lintel-api-build
    package, is now lintel.build in this wheel (extra build).
  • Prepared APIs v1 to v5 (v5 adds task-board commands and relationships) with runtime admission, Relay-style Node IDs and
    connection preflight (v2 to v4 builders need the unpublished
    umf_access_generated_executor and raise UNSUPPORTED without it).
  • The build extra can derive OpenAPI 3.1 and named-operation contracts from an
    admitted prepared API v5 for scalar Record reads, forward pages and declared
    commands. The projection refuses selected relationships and supplies contracts
    for client generation. The served runtime remains GraphQL.
  • lintel.experimental is now shipped in the wheel (extra experimental).
  • Example inputs ship inside the package.
  • Dependencies: umf-core>=0.10.0,<0.11 (tested on 0.10.10), fastapi>=0.135,<1,
    graphql-core>=3.3,<3.4. Removed weft-sql, umf-codegen, umf-access,
    pgserver-pg18 and URL-based dependencies. strawberry-graphql is now only
    needed by the experimental extra.
  • The README quickstart is run against the built wheel in a fresh venv in CI and in the release workflow.
  • Removed the evidence packets and native-read spikes from the tree.

Lintel 0.1.0a1 — experimental direct-UMF projection

Choose a tag to compare

@easel easel released this 04 Nov 04:24

Lintel 0.1.0a1

Release Scope

First experimental Python distribution: lintel-api==0.1.0a1, tag v0.1.0a1,
prepared on 2026-11-03 for PyPI and GitHub. The import namespace is lintel.
This alpha packages the tested direct-UMF scalar projection; it is not the
complete GraphQL/Relay runtime described by the product specifications.

Audience and Channels

Developers exploring UMF-to-GraphQL projection can install the wheel from PyPI.
The GitHub release supplies archives and these notes. Native runtime contributors
can use the source archive's qualification harnesses and governed specifications.

Highlights

  • Direct UMF JSON validation and bounded scalar projection are importable from
    lintel.experimental.projection.
  • lintel.experimental.schema builds the dynamic Strawberry laboratory schema
    and exports deterministic GraphQL SDL.
  • Exact decimal text, canonical UUID, optional-field omission and explicit null
    retain the existing probe behavior.

Required Actions Summary

Install lintel-api==0.1.0a1 with Python 3.11 for the qualified initial profile.
Experimental APIs may change in later alphas. No business-data migration is needed.

Changes and Fixes

The S-01 projection and schema modules move from the source-only spike into the
installed lintel.experimental namespace. Spike harnesses and tests consume those
same modules; the implementation is not duplicated. The source archive includes
S-02 and request-read qualification probes. Native tools are not wheel dependencies.

Release checks pass 47 tests, strict typing, lint, formatting and import boundaries.
A wheel built through the source archive passes an isolated installed query using
9007199254740993.01 without losing decimal precision. Package metadata passes
Twine 7.0.0. These checks do not establish complete product conformance.

Breaking Changes and Required Actions

This is the first published alpha. Source users should replace imports from
spikes.direct_umf.projection and spikes.direct_umf.schema with the corresponding
lintel.experimental modules. No stable public API or prior published migration
is claimed.

Migration or Rollback Guidance

Install the exact alpha version in an isolated environment and follow the
README example. To hold adoption, remove the alpha from that
environment and continue using the prior application environment. Uninstalling
Lintel does not change databases or reverse operations performed by other software.

Known Issues and Support

The probe query and echo mutation are laboratory roots and must not be mounted
as a production API. The wheel does not implement native execution or admission,
Relay identity/pagination, TypeScript client builds, Batten embedding, or managed
Databricks deployment. The separately qualified upstream request-read primitives
are not integrated into a Lintel product API by this release.

Only the recorded scalar subset and Python 3.11 installed profile are qualified.
FastAPI transport and disposable PostgreSQL qualification remain source harnesses.
Report issues at DocumentDrivenDX/lintel.

References

Published to PyPI. Release build, trusted publication and public consumer checks passed.