Skip to content

Phase 2: one version, 3 packages + example, tag-driven release, README - #8

Merged
easel merged 8 commits into
mainfrom
reset/phase2
Nov 11, 2026
Merged

easel merged 8 commits into
mainfrom
reset/phase2

Conversation

@easel

@easel easel commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Phase 2: one version, 3 packages + example, release workflow, README, microsite

Stacked on #7 (base branch reset/phase1); merge #7 first, then retarget/merge this. Nothing is tagged or published.

One version, one tag scheme

All four distributions are 0.1.0a3 (scripts/check_versions.py fails if they differ or do not match the tag). Release tags are v*; the old runtime-v*/storage-v* tags stay as history. This sets the version the next release will carry; it is not a release.

7 packages -> 3 + example (mechanical: git mv, import paths batten.* unchanged)

  • novirhyza-batten = contracts + runtime + tables + asgi (depends on starlette, uvicorn)
  • novirhyza-batten-storage (no dependencies)
  • novirhyza-batten-local = batten.hosting.local + batten.umf_postgres (UMF/Weft/psycopg/pgserver/OpenTelemetry)
  • novirhyza-batten-approval-desk (example; batten-approval)
    The five removed names were never on PyPI. The import-boundary check still enforces the old module separation (ROOTS is keyed by module, not wheel). The wheel-only import test (tests/storage/test_distribution.py) now builds batten and batten-storage.

Python floor

>=3.11,<3.14 (local/example are capped at 3.13 because pgserver-pg18 wheels cover cp310-cp313). Verified locally on 3.11 and 3.13 (98 tests); CI matrix runs 3.11, 3.12 and 3.13.

Dependency ranges

umf-codegen>=0.10.8,<0.11, umf-weft>=0.4.57,<0.5, umf-access>=0.1.0.dev8,<0.2, psycopg[binary]>=3.3.7,<4, pgserver-pg18>=18.6.1,<19, starlette>=1.10,<2, uvicorn>=0.54,<1, opentelemetry-sdk>=1.45,<2; lockstep novirhyza-batten==0.1.0a3. The dev group/uv.lock stay on the currently tested exact versions. A local fresh-venv install picked umf-codegen 0.10.11, umf-core 0.10.11 and psycopg 3.3.8 from the ranges and the quickstart still passed. pgserver-pg18 is not on PyPI: the quickstart and prepare_approval.py use the published GitHub release find-links page.
Follow-up (single item): when umf 0.10.11, umf-weft 0.4.58, umf-access non-dev and pgserver-pg18 on PyPI are released, raise the floors in packages/batten-local/pyproject.toml, refresh uv.lock, and drop the find-links from the README, pyproject.toml and prepare_approval.py.

Release workflow (release.yml)

Triggers: push of a v* tag, or workflow_dispatch (input dry_run, default true; dispatch never publishes). Jobs: test (calls ci.yml), build (version check, scripts/build_dist.py, build-provenance attestation on tags, SHA256SUMS), smoke (fresh venv on Python 3.11 and 3.13; runs the README quickstart verbatim against the built wheels), publish (tag push only; environment pypi; pypa/gh-action-pypi-publish, OIDC, no tokens), github-release (notes from the CHANGELOG section, prerelease). The app wheel has no sdist because it force-includes generated web assets.
ci.yml now also runs check_versions, and the native job builds the wheels and executes the README quickstart (scripts/smoke_install.py).

Docs

README rewritten (what it is, status limited to what CI tests, install + a quickstart that CI executes, packages table, development). It states honestly that Batten ships standalone with no Arras/Lintel/Truss dependency. CHANGELOG.md (seeded from the removed release notes), AGENTS.md updated, ADR-003 notes the new wheel split, guide pages and site README updated, no dead links to deleted files. The microsite home is stamped ALPHA / <version> from packages/batten/pyproject.toml; verify.py checks the stamp.

Acceptance (local, macOS arm64)

  • uv run python scripts/check.py on Python 3.13: green (98 passed); on Python 3.11 (before the collapse): 98 passed.
  • uv run pytest -m integration: 2 passed.
  • scripts/build_dist.py then scripts/smoke_install.py dist (fresh venv, README commands verbatim, PyPI + pgserver release deps): "quickstart OK: registry lists the approval desk".
  • Site build + verify: 7 pages, version stamp present. actionlint on all workflows: clean.
  • CI on this PR: check green on Python 3.11, 3.12 and 3.13 (98 tests each); native green in 3m25s on Linux (integration tests, 2 Playwright scenarios, wheel build, README quickstart against the built wheels); site build green.
  • Not run locally: Python 3.12; the CI matrix covers it. The release workflow itself has not run (it can only be dispatched from the default branch); its building blocks (build_dist.py, smoke_install.py) ran as above.

Known failures

None known.

Owner actions before the first release (not done here)

Create on PyPI a pending trusted publisher for each project: owner DocumentDrivenDX, repository batten, workflow release.yml, environment pypi, for these four project names: novirhyza-batten, novirhyza-batten-storage, novirhyza-batten-local, novirhyza-batten-approval-desk (all currently unclaimed on PyPI). Create the pypi environment in the repo settings. Then tag v0.1.0a3.

Not in this PR

No tag, release or publish; no history rewrite; no integration with Arras/Lintel/Truss (standalone, see ROADMAP.md).

🤖 Generated with Claude Code

easel and others added 7 commits November 11, 2026 17:09
…to the example

Move the approval UMF model from docs/helix/reference-apps to
examples/approval-desk/model (the example wheel and prepare_approval read it).
Delete the 12 reference-app specs, the evidence/verification JSON, boundary
audit, test plan, release notes, the micro-app gate, quality baseline and
ratchet ADRs/contracts; collapse unbuilt work into ROADMAP.md. prepare_approval
installs UMF from PyPI instead of hash-checked release URLs.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Linux-only: unit/lint/type/boundary checks on push and PR; native PostgreSQL
integration and Playwright scenarios on push to main, nightly and dispatch.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
…hon 3.11-3.13

novirhyza-batten (contracts, runtime, tables, asgi), novirhyza-batten-storage,
novirhyza-batten-local (local host + umf_postgres), plus the approval desk.
Import paths are unchanged. Dependency ranges replace exact pins; the old
package names were never on PyPI.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
…oke test

release.yml runs on v* tags (or a dry-run dispatch that never publishes): CI,
build with provenance attestation, fresh-venv smoke on Python 3.11 and 3.13,
PyPI trusted publishing, GitHub Release. CI tests Python 3.11/3.12/3.13 and
executes the README quickstart against the built wheels.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
@easel
easel changed the base branch from reset/phase1 to main November 11, 2026 22:43
main's tree is identical to reset/phase1, which this branch already contains.

Co-Authored-By: Claude Fable 5.2 <[email protected]>
@easel
easel merged commit 2cac0d8 into main Nov 11, 2026
6 checks passed
@easel
easel deleted the reset/phase2 branch November 11, 2026 22:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant