Repository navigation
Phase 2: one version, 3 packages + example, tag-driven release, README - #8
Merged
Merged
Conversation
…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]>
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]>
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]>
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
main's tree is identical to reset/phase1, which this branch already contains. Co-Authored-By: Claude Fable 5.2 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.pyfails if they differ or do not match the tag). Release tags arev*; the oldruntime-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 pathsbatten.*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 (
ROOTSis keyed by module, not wheel). The wheel-only import test (tests/storage/test_distribution.py) now buildsbattenandbatten-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; lockstepnovirhyza-batten==0.1.0a3. The dev group/uv.lockstay 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 andprepare_approval.pyuse 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, refreshuv.lock, and drop the find-links from the README,pyproject.tomlandprepare_approval.py.Release workflow (
release.yml)Triggers: push of a
v*tag, orworkflow_dispatch(inputdry_run, default true; dispatch never publishes). Jobs:test(callsci.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; environmentpypi;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.ymlnow also runscheck_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.mdupdated, ADR-003 notes the new wheel split, guide pages and site README updated, no dead links to deleted files. The microsite home is stampedALPHA / <version>frompackages/batten/pyproject.toml;verify.pychecks the stamp.Acceptance (local, macOS arm64)
uv run python scripts/check.pyon 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.pythenscripts/smoke_install.py dist(fresh venv, README commands verbatim, PyPI + pgserver release deps): "quickstart OK: registry lists the approval desk".actionlinton all workflows: clean.checkgreen on Python 3.11, 3.12 and 3.13 (98 tests each);nativegreen in 3m25s on Linux (integration tests, 2 Playwright scenarios, wheel build, README quickstart against the built wheels); site build green.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, repositorybatten, workflowrelease.yml, environmentpypi, for these four project names:novirhyza-batten,novirhyza-batten-storage,novirhyza-batten-local,novirhyza-batten-approval-desk(all currently unclaimed on PyPI). Create thepypienvironment in the repo settings. Then tagv0.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