← All releases

v0.6.70: Custom domains stay first after an update

Released October 8, 2026 Latest

After an update, setup keeps showing your instance at its custom domain instead of the address Azure generated for it.

Fixes

• Your custom domain stays your instance’s address after an update. If you’ve bound a custom domain to your portal, setup used to show the instance at its generated azurecontainerapps.io address after an Update, until the instance was loaded again. Setup now keeps your custom domain as the instance’s address, and lists the generated address under its other addresses. Setup still checks the update against the generated address, so a DNS or certificate problem with your custom domain can’t fail an update.

How to update

1. Open setup.maester.cloud and sign in with the account you used for setup.
2. Choose your instance and select Update to v0.6.70. The update applies in place, and your stored results and history are untouched.

If you run setup from PowerShell, update the module first with Update-Module MaesterCloud, then run Start-MaesterCloudSetup.