You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Container Apps deploys now fail as soon as Azure knows a revision is broken, instead of waiting out the ten minute readiness timeout, and the error carries the revision's provisioning error or the container's own state and restart count.
Hook output is prefixed with the service it came from, so three package managers printing at once stay readable. Lines are also buffered until complete, so one hook can no longer cut another's line in half.
Changed
Before hooks are now the gate for the whole release rather than for one service — every hook runs first, and if any of them fails nothing is deployed at all. After hooks are unchanged, per service and only on success.
Fixed
A failed Container Apps deploy no longer pays the full readiness timeout twice — the rollback gets its own two minute budget — and a service reverting several targets now does them concurrently instead of one at a time.