Linking 1.0 stable release
APIZIT Linking 1.0.1 is published and verified on PyPI. Pin this exact stable version for reproducible installation. The earlier 0.5 line remains migration history; a stable framework version does not qualify an application's hosting, database or identity policy.
python -m pip install "apizit-linking[preview,models]==1.0.1"The release provides optional nested models and response filtering, body JSON pointers, HTTP status/header policies and safe domain errors, resources and permission guards, lifecycle/middleware hooks, static route composition, routes/explain/export/diff, request IDs and source fingerprints, request bounds and fresh-worker development reload. Ordinary business functions remain callable without a server or APIZIT account.
Manifest version remains 1 and legacy conversion remains the default. Runtime artifacts use format v2 and must be recompiled with the exact engine. Pydantic remains optional. Static validation imports neither factories nor models.
Verified package files#
Trusted Publishing and protected multi-system tests completed before registry verification. Wheel and source archive were downloaded from PyPI 1.0.1 and their SHA-256 values matched the registry:
| File | SHA-256 |
|---|---|
| apizit_linking-1.0.1-py3-none-any.whl | 86bb6fe16892e51d831427ccfe9cdbf3748fe011141fe795ee66453c9c22ceef |
| apizit_linking-1.0.1.tar.gz | 06345b321222aa955c107ed04e12540e3698be7d938ba623551c690a26010bd1 |
A fresh public installation passes CLI/schema/OpenAPI, actual TCP permissions, persistence across process restart and reload, and the public examples. Qualification covers Python 3.10–3.14, minimum dependencies, core-only use and identical double builds. These checks do not establish production throughput, search ranking or AI token savings.
Candidate history and publication status#
The published 1.0.0rc1 candidate exposed a false signature mismatch with inline Annotated[..., Field(...)]. Corrected 1.0.1rc1 passed equivalent-metadata and changed-constraint regressions; stable 1.0.1 finalizes that corrected runtime. Module-level aliases and inline expressions are both supported.
The allocated v1.0.0 tag published no files when GitHub execution was blocked. It was preserved and never reused. Actual registry files establish publication; an allocated tag alone does not. This stable URL records the 1.0 release family, including its first stable registry version 1.0.1.
See migration from 0.5, current limits and standalone serving. The protected APIZIT /linking/ copy and managed runtime adoption have separate dev hosting receipts. No beta or production promotion is implied.