docker-devkit 0.1.11__tar.gz → 0.1.12__tar.gz

{docker_devkit-0.1.11 → docker_devkit-0.1.12}/.github/workflows/release.yml

@@ -28,4 +28,4 @@ jobs:
       - uses: astral-sh/setup-uv@v7
 
       - name: Publish
-        run: uvx --from release-devkit==0.1.3 publish-packages --config publish-config.json
+        run: uvx --from release-devkit==0.1.9 publish-stable --config publish-config.json

{docker_devkit-0.1.11 → docker_devkit-0.1.12}/AGENTS.md

@@ -8,7 +8,7 @@ The package is `docker_devkit` (src-layout under `src/docker_devkit/`); all depe
 
 ## Release flow
 
-Publishing rides `release.yml`, triggered by a successful CI run on a `main` push: the machinery — release-devkit's `publish-packages` (an inlined, version-pinned `uvx` step in the publish job, keeping OIDC identity local), never a project dependency (docker-devkit sits inside its own dependency graph; a project-level release-devkit edge is a resolver cycle) — computes the plan from the tag ledger and path-diff, patches the version ephemerally, and publishes to PyPI under OIDC trusted publishing (publisher bound to `release.yml`, no environment). The committed `pyproject.toml` version is permanently the `0.0.0.dev0` sentinel; the `docker-devkit-v*` tags are the version ledger (first release `0.1.0`, patch-auto thereafter). API-breaking changes ship with a manually bumped version — patch-auto assumes additive changes.
+Publishing rides `release.yml`, triggered by a successful CI run on a `main` push: the machinery — release-devkit's `publish-stable` (an inlined, version-pinned `uvx` step in the publish job, keeping OIDC identity local), never a project dependency (docker-devkit sits inside its own dependency graph; a project-level release-devkit edge is a resolver cycle) — computes the plan from the tag ledger and path-diff, patches the version ephemerally, and publishes to PyPI under OIDC trusted publishing (publisher bound to `release.yml`, no environment). The committed `pyproject.toml` version is permanently the `0.0.0.dev0` sentinel; the `docker-devkit-v*` tags are the version ledger (declared `major_minor` line in `publish-config.json`, patch-auto within the line). API-breaking changes ship with a manually bumped `major_minor` — patch-auto assumes additive changes.
 
 ## Shape
 

{docker_devkit-0.1.11 → docker_devkit-0.1.12}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: docker-devkit
-Version: 0.1.11
+Version: 0.1.12
 Summary: Docker-stack lifecycle commands (up/down/build) with a native/consumer split
 License-File: LICENSE
 License-File: NOTICE

{docker_devkit-0.1.11 → docker_devkit-0.1.12}/publish-config.json

@@ -3,6 +3,7 @@
     {
       "name": "docker-devkit",
       "path": ".",
+      "major_minor": "0.1",
       "feeds": { "pypi": "docker-devkit" }
     }
   ],

{docker_devkit-0.1.11 → docker_devkit-0.1.12}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "docker-devkit"
-version = "0.1.11"
+version = "0.1.12"
 description = "Docker-stack lifecycle commands (up/down/build) with a native/consumer split"
 requires-python = ">=3.13"
 dependencies = [