docker-devkit 0.1.15__tar.gz → 0.1.16__tar.gz

{docker_devkit-0.1.15 → docker_devkit-0.1.16}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: docker-devkit
-Version: 0.1.15
+Version: 0.1.16
 Summary: Docker-stack lifecycle commands (up/down/build) driven by a pyproject-declared compose assembly
 License-File: LICENSE
 License-File: NOTICE

{docker_devkit-0.1.15 → docker_devkit-0.1.16}/plan.md

@@ -1,18 +1,22 @@
 # One home for third-party image declarations; docker-devkit stops parsing compose
 
-Status note for pickup: the docker-devkit half is DONE — redesign executed in
-`2a1fe90` (compose parsing deleted, `declared_references`/`stray_references`
-split, `BakeDocument` base-images validator, typed bake plumbing through
-build/up/down/generate-score, ci-mode registry-cache guard). pytest 77 green,
-ruff + basedpyright clean — the checkpoint's intentional failures are gone.
-Still pending, in order: operator push + tag-ledger release of this repo;
-release-devkit 0.1.11 (`mirror_images.py` → `declared_references`); the
-placeframe PR; capture-tool renames. No consumer repo has been touched yet.
-
-Note on release numbering: the plan projects 0.1.15, but the local tag ledger
-sits at docker-devkit-v0.1.11 with the lifecycle rewrite also unreleased —
-patch-auto will compute the real number at publish time, and the placeframe
-repin must use whatever ships, not the projection.
+Status note for pickup: COMPLETE. Shipped: docker-devkit 0.1.15, release-devkit
+0.1.11 (both on PyPI). placeframe `dev`: `f2c94d16` (declarations conversion +
+generate-score port completion), `33ddfb26` (score artifacts), `e0bcd9f8`
+(prose) — preflight green. capture-tool `dev`: `ef7660d` (renames + repin),
+`6025c5e` (prose) — lock round-trip stable, rig render green. All four repos
+need operator pushes. Resolved during execution: the fluent-bit declaration key
+is `SEAWEEDFS_AUDIT_IMAGE` (the plan's `FLUENT_BIT_IMAGE` never matched the
+actual compose hole — holes stayed textually unchanged); stale `DOTNET_*`
+declarations and `PYTHON_BASE`/`ZED_BASE` lock entries were pruned in placeframe
+(zero consumers); `INITIALIZE_S3_IMAGE` (consumed by scripts/sweep_postprocess)
+was promoted to a declaration; the generate-score console-script collision was
+resolved by completing the port (config table in placeframe pyproject,
+duplicate module deleted); capture-tool's bake file is `compose.bake.yml`, not
+the `compose.zed.bake.yml` this plan named. NEXT: make-it-sing's own plan.md
+resumes — flip its committed Stage 3 checkpoint (`6b4120c`) from
+`ARG UV_BASE_DIGEST` + `FROM mirror/…${UV_BASE_DIGEST}` to
+`ARG UV_BASE_IMAGE` + `FROM ${UV_BASE_IMAGE}`, repin docker-devkit >=0.1.15.
 
 ## Why this initiative exists
 

{docker_devkit-0.1.15 → docker_devkit-0.1.16}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "docker-devkit"
-version = "0.1.15"
+version = "0.1.16"
 description = "Docker-stack lifecycle commands (up/down/build) driven by a pyproject-declared compose assembly"
 requires-python = ">=3.13"
 dependencies = [