The repository or configuration that created this release differ from a previous release. View details.
aiogram-coordination
Source development and releases are maintained in the aiogram-kit monorepo. See the workspace contributing guide; package examples live under packages/aiogram-coordination/.
Shared task-scoped ownership for aiogram applications and independent libraries. The package has no dependency on aiogram-idle, aiogram-nav or aiogram-kit.
Alpha version: 0.1.1. Requires Python 3.10+ and aiogram 3.22–3.x.
pip install aiogram-coordination==0.1.1
# Optional renewable Redis coordination:
pip install 'aiogram-coordination[redis]==0.1.1'
Memory coordination
from aiogram_coordination import CoordinationKey, MemoryCoordinator
coordinator = MemoryCoordinator()
key = CoordinationKey("bot", bot_id=123, chat_id=42, user_id=42)
async def protected_operation():
async with coordinator.hold(key):
scope = coordinator.scope_token(key)
assert scope is not None
# Invoke application code only while this task owns the scope.
Memory scopes serialize one process and one event loop. A child task does not inherit reentrant ownership. Identical structural conversation keys from independent libraries normalize to one full identity; arbitrary generic Hashable keys remain supported by the memory coordinator.
Existing application FSM isolation
Wrap isolation explicitly when constructing the Dispatcher, not after startup:
from aiogram import Dispatcher
from aiogram.fsm.storage.memory import SimpleEventIsolation
from aiogram_coordination import TrackedEventIsolation
application_isolation = SimpleEventIsolation()
tracked = TrackedEventIsolation(application_isolation)
dispatcher = Dispatcher(events_isolation=tracked)
A custom application isolation requires an explicit IsolationProvider tied to
the exact same instance. It must return a key-bound, live LeaseHandle and signal
loss. Unknown opaque locks, disabled isolation and unsupported proof are rejected.
Custom isolation includes the contract and Redis reference.
Redis reference
from aiogram_coordination import RenewableRedisEventIsolation, TrackedEventIsolation
# application_redis is an existing redis.asyncio client owned by your app.
application_isolation = RenewableRedisEventIsolation(redis=application_redis)
tracked = TrackedEventIsolation(application_isolation)
This explicit renewable provider exposes ownership; it does not pretend to renew an opaque aiogram RedisEventIsolation lock. It reuses the caller's Redis client and public aiogram key builder. Client closure remains application-owned.
Use RedisCoordinator(redis=application_redis, prefix="application") for fenced
conversation storage coordination. Its default lease/renew/wait/poll/I/O limits
are 30/10/30/0.05/5 seconds. Lost leases revoke effect authority and cancel owners.
A Lua storage transaction must check the returned fence token and positive PTTL;
a local ownership check cannot make an external API transactional.
External sessions
SessionAuthority.current(key) returns an immutable ExternalSession or None.
It reads only; it never creates, extends or clears application sessions. Outages
raise SessionAuthorityUnavailable and are distinct from missing authorization.
Session rules separate immutable absolute lifetime from a
sliding application inactivity deadline.
Compatibility and verification
| Component | Supported / CI targets |
|---|---|
| Python | 3.10–3.14 |
| aiogram | 3.22 minimum and latest resolvable 3.x |
| Redis client | 5.0.8 minimum and latest below 8, optional |
| Redis server | 7+ single writable primary; CI uses real Redis 7 and 8 |
| Base install | Neither Redis nor Idle/Nav/Kit is required |
CI exercises installed wheels/sdists, task isolation, real Redis renewal/loss and process death. Verification evidence distinguishes executed checks from configured jobs. CONTRIBUTING.md documents commands, SECURITY.md reporting and release guidance the explicit tag-only publication procedure. Nothing configures logging globally on import. The CLI example enables only scoped development debug logging.
MIT licensed; see LICENSE.
Metadata
Release files for aiogram-coordination 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Change of provenance
The repository or configuration that created these release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| aiogram_coordination-0.1.1.tar.gz | 257.8 kB | With provenance | Details for aiogram_coordination-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aiogram_coordination-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for aiogram_coordination-0.1.1-py3-none-any.whl |
Total release size: 279.1 kB
Release files / aiogram_coordination-0.1.1.tar.gz
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | aiogram_coordination-0.1.1.tar.gz |
|---|---|
| Size | 257.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e5ec22b5452c3505c2a9cd46f17894e2381f949fd7f9c179e88f35e9faeb14f7
|
|
BLAKE2b-256 checksum How to use checksums |
68674758a79f5af98581a34c67a4d7e5d02374b95e4e5eb4dd0a860190f1c48d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logRelease files / aiogram_coordination-0.1.1-py3-none-any.whl
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | aiogram_coordination-0.1.1-py3-none-any.whl |
|---|---|
| Size | 21.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e3968449faee82324774f7b9cde8608b842923913e097d362955be5d468c1f68
|
|
BLAKE2b-256 checksum How to use checksums |
6d02a6d2387a56cdc4b4e11af4371bd12fa52c4dfb9263fd69c740eda9d7b88d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logSecurity for aiogram-coordination 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Change of provenance
The repository and configuration that created this release differ from a previous release.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Repository
- Removed 0.1.0 github.com/ArmanAvanesyan/aiogram-coordination
- Added 0.1.1 github.com/ArmanAvanesyan/aiogram-kit
Attestation for aiogram_coordination-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.