chore(release): bump runtime 0.4.1 + contract 0.7.3 (release-prep)

README.md

@@ -255,9 +255,9 @@ A domain repo picks its warehouse engine by which base image it builds
 `FROM`:
 
 ```dockerfile
-FROM ghcr.io/carolsimone/continuo-python-runtime-postgres:v0.4.0
+FROM ghcr.io/carolsimone/continuo-python-runtime-postgres:v0.4.1
 # or
-FROM ghcr.io/carolsimone/continuo-python-runtime-trino:v0.4.0
+FROM ghcr.io/carolsimone/continuo-python-runtime-trino:v0.4.1
 ```
 
 The engine is part of the image **name**; the tag is the bare version, so

adapters/postgres/pyproject.toml

@@ -12,7 +12,7 @@ dependencies = [
     # of this adapter would otherwise accept whatever contract release is
     # newest. This adapter subclasses the contract's WarehouseAdapter port
     # directly, so the pair must stay the tested one.
-    "continuo-engine-contract==0.7.2",
+    "continuo-engine-contract==0.7.3",
     "psycopg2-binary==2.9.12",
     "pyarrow==25.0.1",
 ]

adapters/trino/pyproject.toml

@@ -12,7 +12,7 @@ dependencies = [
     # of this adapter would otherwise accept whatever contract release is
     # newest. This adapter subclasses the contract's WarehouseAdapter port
     # directly, so the pair must stay the tested one.
-    "continuo-engine-contract==0.7.2",
+    "continuo-engine-contract==0.7.3",
     "trino==0.338.0",
     "pyarrow==25.0.1",
 ]

contract/pyproject.toml

@@ -1,5 +1,5 @@
 [project]
-version = "0.7.2"
+version = "0.7.3"
 name = "continuo-engine-contract"
 description = "The contract a Continuo warehouse engine must satisfy: the WarehouseAdapter port and the result-block wire format."
 authors = [{ name = "Simone Carolini" }]

image-requirements-postgres.txt

@@ -1,2 +1,2 @@
-continuo-python-runtime==0.4.0
+continuo-python-runtime==0.4.1
 continuo-postgres-adapter==0.2.0

image-requirements-trino.txt

@@ -1,2 +1,2 @@
-continuo-python-runtime==0.4.0
+continuo-python-runtime==0.4.1
 continuo-trino-adapter==0.2.0

pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "continuo-python-runtime"
-version = "0.4.0"
+version = "0.4.1"
 description = "Runtime harness, contract tooling, and CI lint for Continuo python nodes."
 authors = [{ name = "Simone Carolini" }]
 maintainers = [{ name = "Simone Carolini" }]
@@ -19,7 +19,7 @@ dependencies = [
     # directly. Both packages ship from this repo on one v* tag, so a new
     # contract version never exists without a new runtime version to match it;
     # an exact pin therefore costs nothing and keeps the tested pair together.
-    "continuo-engine-contract==0.7.2",
+    "continuo-engine-contract==0.7.3",
     "boto3==1.43.74",
     "pyarrow==25.0.1",
     "PyYAML==6.0.3",

template/Dockerfile

@@ -1,5 +1,5 @@
 # Tags are v<version>; one image per engine (continuo-python-runtime-postgres / -trino).
-FROM ghcr.io/carolsimone/continuo-python-runtime-postgres:v0.4.0
+FROM ghcr.io/carolsimone/continuo-python-runtime-postgres:v0.4.1
 COPY contracts/ /app/contracts/
 COPY scripts/ /app/scripts/
 # COPY every OTHER directory your scripts import from, too. CI folds a script's

template/requirements.lock

@@ -7,16 +7,16 @@
 # Dockerfile) — they carry no hashes yet, so installing from this file AS-IS
 # WILL FAIL. Do not ship it unmodified.
 #
-# Once continuo-python-runtime==0.4.0 and continuo-postgres-adapter==0.2.0 (or
+# Once continuo-python-runtime==0.4.1 and continuo-postgres-adapter==0.2.0 (or
 # whichever versions you depend on) are published on PyPI, regenerate a real
 # hash-locked file for your engine and versions with:
 #
 #   uv pip compile --generate-hashes --python-version 3.14 - -o template/requirements.lock <<'EOF'
-#   continuo-python-runtime==0.4.0
+#   continuo-python-runtime==0.4.1
 #   continuo-<engine>-adapter==X.Y.Z
 #   EOF
 #
 # Swap <engine>/X.Y.Z for the adapter you actually use (e.g. trino==0.2.0),
 # then commit the regenerated file with its --hash entries.
-continuo-python-runtime==0.4.0
+continuo-python-runtime==0.4.1
 continuo-postgres-adapter==0.2.0