From 7b74d2f5acff538bf6bb1e066f5cbf033b8d3854 Mon Sep 17 00:00:00 2001 From: panopticon-agent Date: Mon, 21 Sep 2026 19:31:23 +0000 Subject: [PATCH] chore: bump project version to 0.1.2 The runner rebuilds a host's base task-container image only when the image's org.panopticon.version label differs from the installed panopticon.__version__ (ImageBuilder.build_base_if_missing). An image whose stamp matches is judged current and is never rebuilt, so moving the version is the switch that makes every host rebuild and pick up whatever now ships inside the image. One hand-edited site: __version__ in src/panopticon/__init__.py. Since #425 pyproject.toml declares dynamic = ["version"] and hatchling reads the value out of the package, so the distribution metadata follows and there is nothing to keep in sync. Co-Authored-By: Claude Opus 5 --- src/panopticon/__init__.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/panopticon/__init__.py b/src/panopticon/__init__.py index 2112a88a..eb625203 100644 --- a/src/panopticon/__init__.py +++ b/src/panopticon/__init__.py @@ -4,4 +4,4 @@ #: ``[project] version`` from this line (``[tool.hatch.version]``). The runner also compares it #: against a base image's ``org.panopticon.version`` label to decide the image is stale #: (``sessionservice/images.py``), so it gates what a host rebuilds, not just what PyPI reports. -__version__ = "0.1.1" +__version__ = "0.1.2"