xtr-orm 2.0.0__tar.gz → 4.0.2__tar.gz

{xtr_orm-2.0.0 → xtr_orm-4.0.2}/LICENSE

@@ -1,6 +1,10 @@
 MIT License
 
 Copyright (c) 2026 xterr
+Copyright (c) 2006-2018 Doctrine Project
+Copyright (c) 2011 Fabien Potencier, Doctrine Project
+Copyright (c) 2006-2013 Doctrine Project
+Copyright (c) 2004-present Fabien Potencier
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

xtr_orm-2.0.0/README.md → xtr_orm-4.0.2/PKG-INFO

@@ -1,3 +1,42 @@
+Metadata-Version: 2.4
+Name: xtr-orm
+Version: 4.0.2
+Summary: Databases for async applications: engines, sessions and versioned schema migrations, configured once per connection.
+Keywords: orm,database,migrations,sqlalchemy,alembic,asyncio
+Author: Xterr
+Author-email: Xterr <me@xterr.dev>
+License-Expression: MIT
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: Framework :: AsyncIO
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Database
+Classifier: Typing :: Typed
+Requires-Dist: advanced-alchemy>=1.11
+Requires-Dist: alembic>=1.20
+Requires-Dist: sqlalchemy[asyncio]>=2.0.41
+Requires-Dist: typing-extensions>=4.4
+Requires-Dist: xtr-logging-contracts>=4.0,<5
+Requires-Dist: xtr-console>=4.0,<5 ; extra == 'console'
+Requires-Dist: xtr-dependency-injection>=4.0,<5 ; extra == 'di'
+Requires-Dist: xtr-service-contracts>=4.0,<5 ; extra == 'di'
+Requires-Dist: xtr-messenger>=4.0,<5 ; extra == 'messenger'
+Requires-Dist: asyncmy>=0.2.9 ; extra == 'mysql'
+Requires-Dist: asyncpg>=0.29 ; extra == 'postgres'
+Requires-Dist: aiosqlite>=0.20 ; extra == 'sqlite'
+Requires-Python: >=3.11
+Provides-Extra: console
+Provides-Extra: di
+Provides-Extra: messenger
+Provides-Extra: mysql
+Provides-Extra: postgres
+Provides-Extra: sqlite
+Description-Content-Type: text/markdown
+
 <div align="center">
 
 # xtr-orm
@@ -163,15 +202,19 @@ removing it undoes.
 - **Install** — `uv add "xtr-orm[di,console,postgres]"`; `mysql` or `sqlite` instead of
   `postgres` for those databases; drop `console` to go without the commands; add `messenger`
   for the [message bus middleware](#message-bus-middleware).
+- **Recipe** — `uv run xtr-recipes recipes:sync` does the *Activate*, *Configure* and
+  *Environment* steps below: it lists `OrmBundle`, writes a starting `<app>/config/orm.py` with the
+  `default` connection, and `DATABASE_URL` in `.env`. It prints the middleware step, which a recipe
+  cannot make for you.
 - **Activate** — `OrmBundle: {"all": True}` in `BUNDLES` in `<app>/bundles.py`, imported from
   `xtr_orm.bundle`.
 - **Brings along** — the logging and console bundles, when those packages are installed.
   With the messenger bundle active too, the [middleware](#message-bus-middleware) are
   registered for a bus to list.
-- **Configure** — optional: with no configuration there is one connection, `default`, reading
-  `DATABASE_URL`, with its revisions in `migrations` in the project directory and diffs
-  against the models advanced-alchemy registers. Connections, replicas and table definitions go
-  in `<app>/config/orm.py`, a `@configure` function returning `OrmConfig` — see
+- **Configure** — the recipe writes a starting `<app>/config/orm.py` with the `default`
+  connection reading `DATABASE_URL`, its revisions in `migrations` in the project directory and
+  diffs against the models advanced-alchemy registers. Add connections, replicas and table
+  definitions to that `@configure` function returning `OrmConfig` — see
   [Kernel / bundle](#kernel--bundle).
 - **Environment** — `DATABASE_URL`, read when a connection is first used — engine, session,
   migrator or command — not when the application boots. Its query may carry options; see
@@ -295,6 +338,82 @@ whatever the one before wrote. Migrations and the database commands always use t
 A block can be sent elsewhere with advanced-alchemy's `primary_context()` and
 `replica_context()`, from `advanced_alchemy.routing`.
 
+## Mapping tables from a bundle
+
+A library can bring its own tables to an application's database — tables whose prefix, names
+or column types the application configures, and which therefore exist only once that
+configuration is read. `OrmMappingsPass` puts them into the table definitions of the
+connection the application picked, while the container is compiled: early enough for
+`orm:migrations:diff` to write them like any of the application's own models.
+
+The library's bundle keeps the pass, registers it in `build`, and hands over the driver it
+builds from its configuration in `load_extension`:
+
+```python
+from xtr_orm.bundle import OrmBundle, OrmMappingsPass
+
+
+@final
+@required_bundle(OrmBundle)
+@as_bundle("invoicing", config=InvoicingConfig)
+class InvoicingBundle(Bundle[InvoicingConfig]):
+    def __init__(self) -> None:
+        self._mappings = OrmMappingsPass("invoicing.connection", "invoicing.persist")
+
+    @override
+    def build(self, builder: ContainerBuilder) -> None:
+        builder.add_compiler_pass(self._mappings)
+
+    @override
+    def load_extension(
+        self, config: InvoicingConfig, services: ServiceConfigurator, builder: ContainerBuilder
+    ) -> None:
+        builder.set_parameter("invoicing.connection", config.connection)
+        builder.set_parameter("invoicing.persist", config.persist)
+        if config.persist:
+            self._mappings.set_driver(InvoicingDriver(config.table_prefix))
+```
+
+A driver is anything satisfying `MappingDriverInterface`: one call, adding its tables and
+naming them. Subclass it to have the type checker hold you to that call.
+
+```python
+from xtr_orm import MappingDriverInterface
+
+
+@final
+class InvoicingDriver(MappingDriverInterface):
+    def __init__(self, prefix: str) -> None:
+        self._prefix = prefix
+
+    def load_metadata(self, metadata: MetaData) -> tuple[str, ...]:
+        name = f"{self._prefix}invoice"
+        if name in metadata.tables:
+            return ()
+        _ = Table(name, metadata, Column("id", Integer, primary_key=True))
+        return (name,)
+```
+
+- **Which definitions** — the ones the connection's migrations compare the database with: its
+  `metadata` when it has one, else the ones advanced-alchemy registers for its `bind_key`. A
+  connection keeping several sets is refused, naming it; give that one a single `MetaData`.
+- **Idempotent, always** — `load_metadata` skips the tables already there and leaves them out
+  of what it returns. The registered definitions are process-wide — advanced-alchemy keeps one
+  `MetaData` per bind key for the whole process — so two kernels in one process load the same
+  driver into the same one. That outlives the flag: a kernel built with the library's
+  persistence off maps nothing itself, yet still *sees* every table a persisting kernel of the
+  same process put in that bind key, or in a module-level `MetaData` both reach, and diffs
+  them as its own. Give such a kernel a `bind_key`, or a freshly built `MetaData`, that no
+  persisting kernel used.
+- **On or off** — the flag parameter is read for truth, and an unset one means off, so a
+  library whose persistence an application turned off maps nothing. On with no driver handed
+  over is refused, as is a connection name nothing configured — both naming what is missing.
+- **Read while compiling** — both parameters are read before `%name%` references are resolved
+  and long before an `env(...)` one is, so a bundle sets them from its own resolved
+  configuration: a plain name and a plain flag. One still holding a `%name%` reference is
+  refused, naming the parameter, as is a connection parameter holding something that is not a
+  name at all — a name is never coerced out of it, since a connection may be called `7`.
+
 ## Console commands
 
 Every command takes `--connection NAME`; the default connection's is used without it. The
@@ -320,15 +439,18 @@ commands that change the database ask first; `-n` answers yes.
 
 `--write-sql` writes to the file named, or to a dated file in the directory named.
 
-Without a container, give the commands their connections once:
+Every command takes the `ConnectionRegistry` it acts on as its one constructor argument — the
+bundle's with a container, and your own without one. Nothing stands in for it: a console with no
+container to supply it reports the parameter it cannot fill.
 
 ```python
 from xtr_orm import ConnectionRegistry, DatabaseManager
-from xtr_orm.command import use_connections
+from xtr_orm.command import MigrationsMigrateCommand
 
 registry = ConnectionRegistry()
 registry.register("default", engine=engine, migrator=migrator, database=DatabaseManager(url))
-use_connections(registry)
+
+migrate = MigrationsMigrateCommand(registry)
 ```
 
 ## Message bus middleware
@@ -410,6 +532,11 @@ every statement committed as it runs, and with every connection parameter of the
 database: the credentials, the host and the driver's query options, such as `ssl`. A SQLite
 database is its file. Any other server is refused with `UnsupportedDatabaseError`.
 
+`create` and `drop` let the server refuse a database that is already there or is not, which is
+why both take a flag — `create(if_not_exists=True)`, `drop(if_exists=True)` — to be told so
+instead. On SQLite the file is the database: dropping one that is not there raises
+`MissingDatabaseError`.
+
 ## Errors
 
 Every error derives from `OrmError`.
@@ -418,6 +545,7 @@ Every error derives from `OrmError`.
 |---|---|
 | `InvalidArgumentError` | A configuration cannot be used — an empty name, an unknown option, a URL option that does not read (also a `ValueError`) |
 | `MigrationError` | A migration is refused or its revisions cannot be read — an unknown or ambiguous version, a revision out of order, a diff of a database behind its revisions |
+| `MissingDatabaseError` | A database is dropped that is not there — a SQLite file that does not exist — without `if_exists` (also a `FileNotFoundError`) |
 | `UnknownConnectionError` | A connection is asked for by a name nothing registered (also a `LookupError`) |
 | `UnsupportedDatabaseError` | A database is created or dropped on a server whose statements are not known |
 | `SessionUnavailableError` | A connection's session is asked for outside a unit of work, or of a connection registered without one |

xtr_orm-2.0.0/PKG-INFO → xtr_orm-4.0.2/README.md

@@ -1,42 +1,3 @@
-Metadata-Version: 2.4
-Name: xtr-orm
-Version: 2.0.0
-Summary: Databases for async applications: engines, sessions and versioned schema migrations, configured once per connection.
-Keywords: orm,database,migrations,sqlalchemy,alembic,asyncio
-Author: Xterr
-Author-email: Xterr <me@xterr.dev>
-License-Expression: MIT
-License-File: LICENSE
-Classifier: Development Status :: 3 - Alpha
-Classifier: Framework :: AsyncIO
-Classifier: Intended Audience :: Developers
-Classifier: Programming Language :: Python :: 3.11
-Classifier: Programming Language :: Python :: 3.12
-Classifier: Programming Language :: Python :: 3.13
-Classifier: Programming Language :: Python :: 3.14
-Classifier: Topic :: Database
-Classifier: Typing :: Typed
-Requires-Dist: advanced-alchemy>=1.11
-Requires-Dist: alembic>=1.20
-Requires-Dist: sqlalchemy[asyncio]>=2.0.41
-Requires-Dist: typing-extensions>=4.4
-Requires-Dist: xtr-logging-contracts>=2.0,<3
-Requires-Dist: xtr-console>=2.0,<3 ; extra == 'console'
-Requires-Dist: xtr-dependency-injection>=2.0,<3 ; extra == 'di'
-Requires-Dist: xtr-service-contracts>=2.0,<3 ; extra == 'di'
-Requires-Dist: xtr-messenger>=2.0,<3 ; extra == 'messenger'
-Requires-Dist: asyncmy>=0.2.9 ; extra == 'mysql'
-Requires-Dist: asyncpg>=0.29 ; extra == 'postgres'
-Requires-Dist: aiosqlite>=0.20 ; extra == 'sqlite'
-Requires-Python: >=3.11
-Provides-Extra: console
-Provides-Extra: di
-Provides-Extra: messenger
-Provides-Extra: mysql
-Provides-Extra: postgres
-Provides-Extra: sqlite
-Description-Content-Type: text/markdown
-
 <div align="center">
 
 # xtr-orm
@@ -202,15 +163,19 @@ removing it undoes.
 - **Install** — `uv add "xtr-orm[di,console,postgres]"`; `mysql` or `sqlite` instead of
   `postgres` for those databases; drop `console` to go without the commands; add `messenger`
   for the [message bus middleware](#message-bus-middleware).
+- **Recipe** — `uv run xtr-recipes recipes:sync` does the *Activate*, *Configure* and
+  *Environment* steps below: it lists `OrmBundle`, writes a starting `<app>/config/orm.py` with the
+  `default` connection, and `DATABASE_URL` in `.env`. It prints the middleware step, which a recipe
+  cannot make for you.
 - **Activate** — `OrmBundle: {"all": True}` in `BUNDLES` in `<app>/bundles.py`, imported from
   `xtr_orm.bundle`.
 - **Brings along** — the logging and console bundles, when those packages are installed.
   With the messenger bundle active too, the [middleware](#message-bus-middleware) are
   registered for a bus to list.
-- **Configure** — optional: with no configuration there is one connection, `default`, reading
-  `DATABASE_URL`, with its revisions in `migrations` in the project directory and diffs
-  against the models advanced-alchemy registers. Connections, replicas and table definitions go
-  in `<app>/config/orm.py`, a `@configure` function returning `OrmConfig` — see
+- **Configure** — the recipe writes a starting `<app>/config/orm.py` with the `default`
+  connection reading `DATABASE_URL`, its revisions in `migrations` in the project directory and
+  diffs against the models advanced-alchemy registers. Add connections, replicas and table
+  definitions to that `@configure` function returning `OrmConfig` — see
   [Kernel / bundle](#kernel--bundle).
 - **Environment** — `DATABASE_URL`, read when a connection is first used — engine, session,
   migrator or command — not when the application boots. Its query may carry options; see
@@ -334,6 +299,82 @@ whatever the one before wrote. Migrations and the database commands always use t
 A block can be sent elsewhere with advanced-alchemy's `primary_context()` and
 `replica_context()`, from `advanced_alchemy.routing`.
 
+## Mapping tables from a bundle
+
+A library can bring its own tables to an application's database — tables whose prefix, names
+or column types the application configures, and which therefore exist only once that
+configuration is read. `OrmMappingsPass` puts them into the table definitions of the
+connection the application picked, while the container is compiled: early enough for
+`orm:migrations:diff` to write them like any of the application's own models.
+
+The library's bundle keeps the pass, registers it in `build`, and hands over the driver it
+builds from its configuration in `load_extension`:
+
+```python
+from xtr_orm.bundle import OrmBundle, OrmMappingsPass
+
+
+@final
+@required_bundle(OrmBundle)
+@as_bundle("invoicing", config=InvoicingConfig)
+class InvoicingBundle(Bundle[InvoicingConfig]):
+    def __init__(self) -> None:
+        self._mappings = OrmMappingsPass("invoicing.connection", "invoicing.persist")
+
+    @override
+    def build(self, builder: ContainerBuilder) -> None:
+        builder.add_compiler_pass(self._mappings)
+
+    @override
+    def load_extension(
+        self, config: InvoicingConfig, services: ServiceConfigurator, builder: ContainerBuilder
+    ) -> None:
+        builder.set_parameter("invoicing.connection", config.connection)
+        builder.set_parameter("invoicing.persist", config.persist)
+        if config.persist:
+            self._mappings.set_driver(InvoicingDriver(config.table_prefix))
+```
+
+A driver is anything satisfying `MappingDriverInterface`: one call, adding its tables and
+naming them. Subclass it to have the type checker hold you to that call.
+
+```python
+from xtr_orm import MappingDriverInterface
+
+
+@final
+class InvoicingDriver(MappingDriverInterface):
+    def __init__(self, prefix: str) -> None:
+        self._prefix = prefix
+
+    def load_metadata(self, metadata: MetaData) -> tuple[str, ...]:
+        name = f"{self._prefix}invoice"
+        if name in metadata.tables:
+            return ()
+        _ = Table(name, metadata, Column("id", Integer, primary_key=True))
+        return (name,)
+```
+
+- **Which definitions** — the ones the connection's migrations compare the database with: its
+  `metadata` when it has one, else the ones advanced-alchemy registers for its `bind_key`. A
+  connection keeping several sets is refused, naming it; give that one a single `MetaData`.
+- **Idempotent, always** — `load_metadata` skips the tables already there and leaves them out
+  of what it returns. The registered definitions are process-wide — advanced-alchemy keeps one
+  `MetaData` per bind key for the whole process — so two kernels in one process load the same
+  driver into the same one. That outlives the flag: a kernel built with the library's
+  persistence off maps nothing itself, yet still *sees* every table a persisting kernel of the
+  same process put in that bind key, or in a module-level `MetaData` both reach, and diffs
+  them as its own. Give such a kernel a `bind_key`, or a freshly built `MetaData`, that no
+  persisting kernel used.
+- **On or off** — the flag parameter is read for truth, and an unset one means off, so a
+  library whose persistence an application turned off maps nothing. On with no driver handed
+  over is refused, as is a connection name nothing configured — both naming what is missing.
+- **Read while compiling** — both parameters are read before `%name%` references are resolved
+  and long before an `env(...)` one is, so a bundle sets them from its own resolved
+  configuration: a plain name and a plain flag. One still holding a `%name%` reference is
+  refused, naming the parameter, as is a connection parameter holding something that is not a
+  name at all — a name is never coerced out of it, since a connection may be called `7`.
+
 ## Console commands
 
 Every command takes `--connection NAME`; the default connection's is used without it. The
@@ -359,15 +400,18 @@ commands that change the database ask first; `-n` answers yes.
 
 `--write-sql` writes to the file named, or to a dated file in the directory named.
 
-Without a container, give the commands their connections once:
+Every command takes the `ConnectionRegistry` it acts on as its one constructor argument — the
+bundle's with a container, and your own without one. Nothing stands in for it: a console with no
+container to supply it reports the parameter it cannot fill.
 
 ```python
 from xtr_orm import ConnectionRegistry, DatabaseManager
-from xtr_orm.command import use_connections
+from xtr_orm.command import MigrationsMigrateCommand
 
 registry = ConnectionRegistry()
 registry.register("default", engine=engine, migrator=migrator, database=DatabaseManager(url))
-use_connections(registry)
+
+migrate = MigrationsMigrateCommand(registry)
 ```
 
 ## Message bus middleware
@@ -449,6 +493,11 @@ every statement committed as it runs, and with every connection parameter of the
 database: the credentials, the host and the driver's query options, such as `ssl`. A SQLite
 database is its file. Any other server is refused with `UnsupportedDatabaseError`.
 
+`create` and `drop` let the server refuse a database that is already there or is not, which is
+why both take a flag — `create(if_not_exists=True)`, `drop(if_exists=True)` — to be told so
+instead. On SQLite the file is the database: dropping one that is not there raises
+`MissingDatabaseError`.
+
 ## Errors
 
 Every error derives from `OrmError`.
@@ -457,6 +506,7 @@ Every error derives from `OrmError`.
 |---|---|
 | `InvalidArgumentError` | A configuration cannot be used — an empty name, an unknown option, a URL option that does not read (also a `ValueError`) |
 | `MigrationError` | A migration is refused or its revisions cannot be read — an unknown or ambiguous version, a revision out of order, a diff of a database behind its revisions |
+| `MissingDatabaseError` | A database is dropped that is not there — a SQLite file that does not exist — without `if_exists` (also a `FileNotFoundError`) |
 | `UnknownConnectionError` | A connection is asked for by a name nothing registered (also a `LookupError`) |
 | `UnsupportedDatabaseError` | A database is created or dropped on a server whose statements are not known |
 | `SessionUnavailableError` | A connection's session is asked for outside a unit of work, or of a connection registered without one |

{xtr_orm-2.0.0 → xtr_orm-4.0.2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "xtr-orm"
-version = "2.0.0"
+version = "4.0.2"
 description = "Databases for async applications: engines, sessions and versioned schema migrations, configured once per connection."
 readme = "README.md"
 requires-python = ">=3.11"
@@ -30,7 +30,7 @@ dependencies = [
     "alembic>=1.20",
     "sqlalchemy[asyncio]>=2.0.41",
     "typing-extensions>=4.4",
-    "xtr-logging-contracts>=2.0,<3",
+    "xtr-logging-contracts>=4.0,<5",
 ]
 
 [[project.authors]]
@@ -42,15 +42,18 @@ postgres = ["asyncpg>=0.29"]
 sqlite = ["aiosqlite>=0.20"]
 mysql = ["asyncmy>=0.2.9"]
 di = [
-    "xtr-dependency-injection>=2.0,<3",
-    "xtr-service-contracts>=2.0,<3",
+    "xtr-dependency-injection>=4.0,<5",
+    "xtr-service-contracts>=4.0,<5",
 ]
-console = ["xtr-console>=2.0,<3"]
-messenger = ["xtr-messenger>=2.0,<3"]
+console = ["xtr-console>=4.0,<5"]
+messenger = ["xtr-messenger>=4.0,<5"]
 
 [project.entry-points."xtr_dependency_injection.bundles"]
 orm = "xtr_orm.bundle:OrmBundle"
 
+[project.entry-points.xtr_recipes]
+orm = "xtr_orm.recipe"
+
 [dependency-groups]
 dev = [
     "basedpyright>=1.21",
@@ -60,11 +63,11 @@ dev = [
     "anyio>=4.0",
     "ty>=0.0.83",
     "aiosqlite>=0.20",
-    "xtr-console>=2.0,<3",
-    "xtr-dependency-injection>=2.0,<3",
-    "xtr-logging>=2.0,<3",
-    "xtr-messenger>=2.0,<3",
-    "xtr-service-contracts>=2.0,<3",
+    "xtr-console>=4.0,<5",
+    "xtr-dependency-injection>=4.0,<5",
+    "xtr-logging>=4.0,<5",
+    "xtr-messenger>=4.0,<5",
+    "xtr-service-contracts>=4.0,<5",
 ]
 
 [build-system]

{xtr_orm-2.0.0 → xtr_orm-4.0.2}/pyproject.toml.orig

@@ -1,6 +1,6 @@
 [project]
 name = "xtr-orm"
-version = "2.0.0"
+version = "4.0.2"
 description = "Databases for async applications: engines, sessions and versioned schema migrations, configured once per connection."
 readme = "README.md"
 requires-python = ">=3.11"
@@ -26,7 +26,7 @@ dependencies = [
     "alembic>=1.20",
     "sqlalchemy[asyncio]>=2.0.41",
     "typing-extensions>=4.4",
-    "xtr-logging-contracts>=2.0,<3",
+    "xtr-logging-contracts>=4.0,<5",
 ]
 
 [project.optional-dependencies]
@@ -40,14 +40,14 @@ mysql = [
     "asyncmy>=0.2.9",
 ]
 di = [
-    "xtr-dependency-injection>=2.0,<3",
-    "xtr-service-contracts>=2.0,<3",
+    "xtr-dependency-injection>=4.0,<5",
+    "xtr-service-contracts>=4.0,<5",
 ]
 console = [
-    "xtr-console>=2.0,<3",
+    "xtr-console>=4.0,<5",
 ]
 messenger = [
-    "xtr-messenger>=2.0,<3",
+    "xtr-messenger>=4.0,<5",
 ]
 
 # Advertises the bundle so debug:bundles can name it when installed but not listed.
@@ -55,6 +55,10 @@ messenger = [
 [project.entry-points."xtr_dependency_injection.bundles"]
 orm = "xtr_orm.bundle:OrmBundle"
 
+# Advertises the recipe — what *Use in an application* takes — for recipes:sync.
+[project.entry-points."xtr_recipes"]
+orm = "xtr_orm.recipe"
+
 [dependency-groups]
 dev = [
     "basedpyright>=1.21",
@@ -65,11 +69,11 @@ dev = [
     "ty>=0.0.83",
     # Every test runs on SQLite files under the test's own directory: no server.
     "aiosqlite>=0.20",
-    "xtr-console>=2.0,<3",
-    "xtr-dependency-injection>=2.0,<3",
-    "xtr-logging>=2.0,<3",
-    "xtr-messenger>=2.0,<3",
-    "xtr-service-contracts>=2.0,<3",
+    "xtr-console>=4.0,<5",
+    "xtr-dependency-injection>=4.0,<5",
+    "xtr-logging>=4.0,<5",
+    "xtr-messenger>=4.0,<5",
+    "xtr-service-contracts>=4.0,<5",
 ]
 
 [build-system]