Changelog

Fixes and improvements, early November

Fixes and smaller improvements shipped in the first part of November.

  • A release of a one-replica container on machines keeps the old replica serving until the new one is healthy. When the pool can grow, Alien adds a machine first. Machines a release leaves empty are returned.
  • When a container on machines exits on its own, its events show the exit and its code, instead of a scale-down. The deployment page shows these events under Runtime events.
  • Logs from containers Alien adds to a deployment, such as the sandbox egress gateway, are labeled as system output and hidden by default.
  • A failed automatic update reads Update failed while the previous release keeps serving, a retried update shows as queued until it's picked up, and containers no longer read Degraded while an update runs or Not reporting right after a long one.
  • When an update waits for initial setup, the deployment says Action required with numbered steps for its setup method, and a customer-installed deployment offers Send to customer. Optional features that need initial setup say auto-updates continue either way.
  • A release that replaces a failing update is applied, instead of waiting behind it.
  • A daemon can update while its cluster replaces machines, a roll never drains a daemon's last healthy load balancer target, a failed roll cancels its drains, and rolls and scale-in keep zones balanced.
  • The deploy page and setup links offer only the platforms a release was built for, and subaccounts only on those clouds.
  • Secret inputs keep their line breaks, and a PEM value pasted as one line is refused. Running initial setup again can replace an old input value the release no longer accepts.
  • A Private Alien Instance's custom domain gets its TLS certificate, and is released when the instance is uninstalled. Deleting an instance revokes its setup links.
  • On AWS, ai/invoke can list Bedrock inference profiles and Bedrock Mantle models, so model discovery works where invoking already did.
  • AWS image pushes go through the registry proxy in chunks, so large images upload reliably.
  • TypeScript containers keep requests that stay silent for more than 10 seconds, and entry files that use import.meta.main compile.
  • alien dev creates its deployment with stack inputs, and a container can use a linked Sandbox.
  • Air-gapped sites receive every image layer after their registry changes.
  • The CLI says who approves an access request, and a debug session ends when its access is revoked.
  • Errors from AWS KMS, SSM, and Secrets Manager no longer include secret values.