# L4 0.2.18

> This release fixes Factory provisioning completion against the live Cloudflare Containers response. Landing, Shell, installer, Server, portable runtime and Docs share 0.2.18. Existing customer Servers stay pinned until…

Source: https://llll.gg/changelog/v0.2.18

This release fixes Factory provisioning completion against the live Cloudflare Containers response. Landing, Shell, installer, Server, portable runtime and Docs share **0.2.18**. Existing customer Servers stay pinned until their operator chooses an update.

Cloudflare may return the selected instance size as `vcpu`, `memory_mib` and `disk.size_mb`, omitting `instance_type`. The installer now recognizes either representation and verifies the exact reviewed CPU, RAM and decimal disk capacity. Missing, contradictory or different sizes still fail closed. This prevents a completed image rollout from being reported as pending and avoids unnecessary repair when an existing configuration already matches.

For a failed unused Factory repair on 0.2.17, retry **Review Factory provisioning** through the updated official installer with the same reviewed resources. A successful retry releases the activation fence only after image, size and namespace match. Existing Nodes and retained Task source remain protected. No source, Server data, credentials or backup destinations are removed.

The image-layer fixes, unused-repair activation fencing and installer recovery from 0.2.16–0.2.17 remain in place. Published artifacts are unchanged. No Server SQL or Durable Object migration is required.