Skip to content

v0.74.0

Choose a tag to compare

@steipete steipete released this 11 Oct 03:44
· 163 commits to main since this release
Immutable release. Only release title and notes can be modified.
v0.74.0
338eb4a

0.74.0 - 2026-10-10

Highlights

  • Recover GitHub Codespaces leases safely after interrupted requests. Caller-supplied lease IDs now bind recovery to the exact account and creation intent, with receipts that prevent accidental recreation. PR 2752, Issue 2660. Thanks @jcxmt125.
  • Start exe.dev leases from a prepared VM. Use --exe-dev-from to copy a ready workspace into a separately owned lease with fresh ownership tags and a persistent work root. PR 2757, PR 2754. Thanks @salmonumbrella.
  • See what AWS capacity checks actually know. Doctor distinguishes sufficient quota from unchecked regional usage instead of reporting available capacity from the quota ceiling alone. PR 2753. Thanks @vincentkoc.
  • Run more concurrent coordinator leases. Fleet, org, and capacity-admin active-lease caps rise from 20 to 50; the ordinary owner cap and monthly budgets remain unchanged. PR 2756.

Upgrade notes

  • Automation parsing AWS doctor capacity output should handle capacity=unknown quota_limit=sufficient usage=unchecked region=...: a sufficient quota no longer implies available regional capacity. PR 2753. Thanks @vincentkoc.

Added

  • exe.dev: start separately claimed leases from prepared VMs with --exe-dev-from, fresh ownership tags, and persistent work roots while preserving existing claim paths. PR 2757, PR 2754. Thanks @salmonumbrella.
  • GitHub Codespaces: support replay-safe caller-supplied lease IDs with account- and intent-bound recovery, exact-resource cleanup, and terminal receipts. PR 2752, Issue 2660. Thanks @jcxmt125.

Changes

  • Coordinator: raise fleet, org, and capacity-admin active-lease caps from 20 to 50, preserving the ordinary owner cap and monthly budgets. PR 2756.

Fixes

  • AWS: stop reporting available capacity from quota ceilings alone; mark regional usage unchecked and clarify that class fallback still requires quota headroom. PR 2753. Thanks @vincentkoc.
  • DigitalOcean: prefer the first available region near San Francisco when no region is configured, preserve explicit regions, and reuse the recorded region on fixed-lease replay. PR 2758.
  • Azure: refuse retained network-companion cleanup when provider-key or fixed-attempt tags conflict with the original claim, even when immutable resource IDs still match. PR 2751.