chore(release): 0.8.0 (DuckDB adapter, verified multi-arch release pipeline)

CHANGELOG.md

@@ -5,6 +5,8 @@ follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+## [0.8.0] - 2026-10-01
+
 ### Added
 
 - `continuo-duckdb-adapter` 0.1.0: a DuckDB engine adapter on a DuckLake
@@ -53,6 +55,10 @@ follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 - `release.yml` waits only for `publish-pypi.yml`, which now covers the images,
   and selects that tag's own run (a `-test` rehearsal on the same commit no
   longer shares its lookup).
+- `continuo-python-runtime` 0.7.0 → 0.8.0. `continuo-engine-contract`,
+  `continuo-postgres-adapter` and `continuo-trino-adapter` are unchanged;
+  `continuo-duckdb-adapter` 0.1.0 is new, and `continuo-python-runtime-duckdb`
+  is the third engine image published per tag.
 
 ### Fixed
 

README.md

@@ -266,18 +266,21 @@ A domain repo picks its warehouse engine by which base image it builds
 `FROM`:
 
 ```dockerfile
-FROM ghcr.io/carolsimone/continuo-python-runtime-postgres:v0.7.0
+FROM ghcr.io/carolsimone/continuo-python-runtime-postgres:v0.8.0
 # or
-FROM ghcr.io/carolsimone/continuo-python-runtime-trino:v0.7.0
+FROM ghcr.io/carolsimone/continuo-python-runtime-trino:v0.8.0
+# or
+FROM ghcr.io/carolsimone/continuo-python-runtime-duckdb:v0.8.0
 ```
 
 The engine is part of the image **name**; the tag is the bare version, so
 Continuo's Helm chart can pin an image as `<name>:vX.Y.Z@sha256:<digest>`.
 
 Each image bakes in exactly one `WarehouseAdapter` for that engine — the
-pinned PyPI version of the `continuo-postgres-adapter` or
-`continuo-trino-adapter` package built from this repo's `adapters/postgres/`
-or `adapters/trino/` source (see the table above) — registered under the
+pinned PyPI version of the `continuo-postgres-adapter`,
+`continuo-trino-adapter` or `continuo-duckdb-adapter` package built from this
+repo's `adapters/postgres/`, `adapters/trino/` or `adapters/duckdb/` source
+(see the table above) — registered under the
 `continuo_engine.adapters` entry-point group (entry names `postgres` /
 `trino` / `duckdb`). The runtime discovers it via `discover_adapter()` at run time, so a
 single image serves every node in the service and the release-time

image-requirements-duckdb.txt

@@ -1,3 +1,3 @@
-continuo-python-runtime==0.7.0
+continuo-python-runtime==0.8.0
 continuo-duckdb-adapter==0.1.0
 continuo-engine-contract==0.7.3

image-requirements-postgres.txt

@@ -1,3 +1,3 @@
-continuo-python-runtime==0.7.0
+continuo-python-runtime==0.8.0
 continuo-postgres-adapter==0.2.2
 continuo-engine-contract==0.7.3

image-requirements-trino.txt

@@ -1,3 +1,3 @@
-continuo-python-runtime==0.7.0
+continuo-python-runtime==0.8.0
 continuo-trino-adapter==0.2.1
 continuo-engine-contract==0.7.3

pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "continuo-python-runtime"
-version = "0.7.0"
+version = "0.8.0"
 description = "Runtime harness, contract tooling, and CI lint for Continuo python nodes."
 authors = [{ name = "Simone Carolini" }]
 maintainers = [{ name = "Simone Carolini" }]

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.7.0
+FROM ghcr.io/carolsimone/continuo-python-runtime-postgres:v0.8.0
 COPY contracts/ /app/contracts/
 COPY scripts/ /app/scripts/
 # COPY every OTHER directory your scripts import from, too. CI folds a script's