Skip to content

v0.12.4

A workspace on an ecs-ec2 deployment could not start after upgrading to 0.12.3. This release fixes that; upgrade straight to it.

  • On ecs-ec2, upgrading to 0.12.3 left every existing workspace unable to start, with Availability Zone Rebalancing does not support maximumPercent <= 100 %. 0.12.3 began pinning each workspace’s service to one task at a time, which Amazon ECS refuses while Availability Zone rebalancing is switched on for that service. Rebalancing is decided when a service is created, so only workspaces that existed before the upgrade were affected — a workspace created on 0.12.3 starts normally. Rebalancing is now switched off explicitly whenever the service is updated, which also matches how these services work: a workspace’s task is pinned to the machine holding its home disk, so there is no other Availability Zone for it to move to.

Nothing to do beyond deploying: each workspace’s service is corrected the next time it starts. If you upgraded to 0.12.3 and worked around this by hand, that stays valid.