dsoxlab 0.2.3__tar.gz → 0.2.4__tar.gz

{dsoxlab-0.2.3 → dsoxlab-0.2.4}/.github/workflows/appliance.yml

@@ -110,9 +110,15 @@ jobs:
         # this workflow died on exactly that, four hundredths of a second in —
         # a defect no local build could show, since the directory exists and is
         # writable on a developer's machine.
+        #
+        # `out/` is deliberately NOT created: Packer refuses to start when its
+        # output directory already exists ("It must not exist"), which is how
+        # it guarantees it never writes over a previous build. Creating it here
+        # traded one failure for another, one step later — measured on the
+        # second real run.
         run: |
           set -euo pipefail
-          sudo mkdir -p "${BUILD_DIR}/out" "${BUILD_DIR}/tmp"
+          sudo mkdir -p "${BUILD_DIR}/tmp"
           sudo chown -R "$(id -u):$(id -g)" "${BUILD_DIR}"
           df -h "${BUILD_DIR}"
 

{dsoxlab-0.2.3 → dsoxlab-0.2.4}/CHANGELOG.fr.md

@@ -9,6 +9,21 @@ et le projet suit le [versionnage sémantique](https://semver.org/lang/fr/).
 
 ## [Non publié]
 
+## [0.2.4] - 2026-09-26
+
+### Corrigé
+
+- **Le build de l'appliance a avancé d'une étape, et s'est arrêté sur la
+  précédente.** `/mnt` étant enfin accessible en écriture, c'est Packer qui a
+  refusé de démarrer : *Output directory '/mnt/appliance/out' already exists.
+  It must not exist.* Ce refus est une qualité — c'est ainsi que Packer
+  garantit qu'il n'écrase jamais un build précédent — et l'étape de
+  préparation créait précisément ce répertoire. Elle ne crée plus que le
+  parent et le répertoire temporaire, et laisse `out/` à Packer. Deux échecs
+  de suite au même endroit disent quelque chose qu'il vaut la peine de
+  retenir : un workflow qui n'a jamais tourné est un workflow qui ne marche
+  pas, et le seul moyen de le savoir est de le jouer.
+
 ## [0.2.3] - 2026-09-26
 
 ### Corrigé

{dsoxlab-0.2.3 → dsoxlab-0.2.4}/CHANGELOG.md

@@ -9,6 +9,20 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.2.4] - 2026-09-26
+
+### Fixed
+
+- **The appliance build got one step further, and stopped on the step before.**
+  With `/mnt` finally writable, Packer refused to start: *Output directory
+  '/mnt/appliance/out' already exists. It must not exist.* That refusal is a
+  feature — it is how Packer guarantees it never writes over a previous
+  build — and the preparation step was creating that very directory. It now
+  creates only the parent and the temporary directory, and leaves `out/` to
+  Packer. Two failures in a row at the same place say something worth keeping:
+  a workflow that has never run is a workflow that does not work, and the only
+  way to know is to run it.
+
 ## [0.2.3] - 2026-09-26
 
 ### Fixed

{dsoxlab-0.2.3 → dsoxlab-0.2.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: dsoxlab
-Version: 0.2.3
+Version: 0.2.4
 Summary: Turn declarative exercises into reproducible, runnable and verifiable lab environments
 Project-URL: Homepage, https://blog.stephane-robert.info/
 Project-URL: Documentation, https://github.com/stephrobert/dsoxlab/blob/main/docs/README.md

{dsoxlab-0.2.3 → dsoxlab-0.2.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "dsoxlab"
-version = "0.2.3"
+version = "0.2.4"
 description = "Turn declarative exercises into reproducible, runnable and verifiable lab environments"
 readme = "README.md"
 requires-python = ">=3.11"

{dsoxlab-0.2.3 → dsoxlab-0.2.4}/uv.lock

@@ -290,7 +290,7 @@ wheels = [
 
 [[package]]
 name = "dsoxlab"
-version = "0.2.3"
+version = "0.2.4"
 source = { editable = "." }
 dependencies = [
     { name = "ansible-core" },