Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions planning/releases/0.1.2.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
# compose2pod 0.1.2 — accept the service `hostname` key

A patch release that stops rejecting valid compose documents which set a
service `hostname`. The validator was over-strict: a service carrying
`hostname:` — used to give a service a stable name that other services connect
to — raised `unsupported key 'hostname'`. Such documents now convert.

## Fix

- **The service `hostname` key is accepted.** `validate()` no longer rejects a
service that sets `hostname:`, and the hostname is made resolvable to
`127.0.0.1` inside the pod, exactly like a network alias: it joins the
`--add-host` set so other services reach the service by that name. Because all
services share one network namespace (and the pod's UTS namespace), only name
resolution is meaningful — no per-container `--hostname` is emitted.

## Downstream

No action needed — additive and backward compatible. Documents that previously
failed with `unsupported key 'hostname'` now emit a pod script; nothing that
converted before changes.

## Internals

- `architecture/supported-subset.md` adds `hostname` to the supported
service-key matrix with the shared-namespace resolution rationale.
- 86 tests at 100% line coverage (enforced); `ruff select=ALL`, `ty`, and
`eof-fixer` clean.