diff --git a/planning/releases/0.1.4.md b/planning/releases/0.1.4.md
new file mode 100644
index 0000000..bb7a7ed
--- /dev/null
+++ b/planning/releases/0.1.4.md
@@ -0,0 +1,32 @@
+# compose2pod 0.1.4 — accept the service `container_name` key
+
+A patch release that stops rejecting valid compose documents which set a
+service `container_name`. The validator was over-strict: a service carrying
+`container_name:` — used to give a service a stable name that other services
+connect to — raised `unsupported key 'container_name'`. Such documents now
+convert.
+
+## Fix
+
+- **The service `container_name` key is accepted.** `validate()` no longer
+  rejects a service that sets `container_name:`, and the name is made
+  resolvable to `127.0.0.1` inside the pod, exactly like `hostname` and network
+  aliases already are: it joins the `--add-host` set so other services reach it
+  by that name. The actual podman container keeps its internal
+  `{pod}-{service}` name (used for `podman cp`, healthcheck polling, and
+  diagnostics) — only name resolution is affected, matching the pod's
+  shared network namespace.
+
+## Downstream
+
+No action needed — additive and backward compatible. Documents that previously
+failed with `unsupported key 'container_name'` now emit a pod script; nothing
+that converted before changes.
+
+## Internals
+
+- `architecture/supported-subset.md` merges the `hostname`/`container_name`
+  note explaining both are shared-namespace-resolvable but never change the
+  real `--name`.
+- 92 tests at 100% line coverage (enforced); `ruff select=ALL`, `ty`, and
+  `eof-fixer` clean.