Skip to content

Monorepo development and independent releases

All library source is under packages/. Distribution names and Python imports are unchanged. aiogram-coordination remains a neutral distribution. Neither Nav nor Idle requires the other; Idle's nav extra explicitly enables their integration. Redis remains optional.

The root uv workspace and lockfile support joint development. Package-local locks support isolated compatibility CI: each workflow stages one package, preserving its own declared Python and dependency endpoints, then installs matching peer wheels built from this checkout. The staging process is generated by tools/port_ci.py; package-local workflow files are preserved migration inputs, not active workflows. Build and install artifacts outside the workspace before releasing; editable workspace resolution is insufficient evidence.

Releases

Release each distribution independently using <distribution>-v<version> tags. Publication runs only through the corresponding publish-<distribution>.yml workflow on that tag, with an independently reviewed SHA256 digest of the release's SHA256SUMS. The workflow downloads, verifies and publishes the exact reviewed wheel and sdist; it never rebuilds them.

Native companions retain their separate projects and performance gates. Their proposed tag format is <distribution>-native-v<version>. Native publication remains withheld until the existing benchmark and platform gates pass; base migration releases do not enable it.

Historical records

reports/monorepo-migration/ records source repository identities, preserved refs, document locations and Kit working-copy hashes. Original commit IDs remain unchanged. Historical Git checkouts retain their original layout; migration commits introduce the package directories. Git history does not contain GitHub issues, PRs, projects, releases or assets. These have a separate inventory and cutover checklist. The five retiring repositories were archived on 2026-11-17 after the preservation and release gates passed. The six obsolete publisher bindings were removed; each package publishes only through its matching monorepo workflow. See the migration status report for verified evidence. Do not reuse the old Sentinel repository name.

The migration patch changes native identity versions without changing their ABI or kernel behavior. Applications opting into source-built native engines must rebuild the matching companion. Python remains the default; this migration requires no Redis data-format change.

Cross-package benchmark orchestration is under tools/optimization/; package-owned drivers remain under each package's benchmarks/. The controller defaults to this workspace's packages/ directory and still accepts an explicit external repository directory.

Git-based installations

PyPI names and Python imports are unchanged. New Git-based installations select the package subdirectory and its independent tag, for example:

pip install 'git+https://github.com/ArmanAvanesyan/aiogram-kit.git@aiogram-nav-v0.3.1#subdirectory=packages/aiogram-nav'

An unqualified install from the repository root is not a library installation. Historical Git tags retain their original layouts. Update floating Sentinel Git URLs and CI checkout commands to select the new subdirectory; GitHub's repository redirect does not add it.

Ongoing verification

Main runs the complete package and shared-tool matrix. Documentation deploys automatically from main; PR builds have no deployment permissions. Independent publishers recheck the reviewed manifest after downloading the producer's immutable Actions artifact, before copying only the two verified distributions into the publishing directory.

Check or regenerate the shared publisher handoff with:

uv run --no-sync python tools/publish_handoff.py
uv run --no-sync python tools/publish_handoff.py --write

From a full clone with the canonical origin, verify original ancestry, protected working files and advertised history refs with:

uv run --no-sync python tools/verify_migration.py --historical-objects --remote-refs

The post-cutover review records the review findings and release/preservation evidence.