Andras BacsaiandClaude Opus 5.5 1bebdffaff fix(deploy): keep the healthy new container when a rolling update fails late ...

Laravel runs failed() on a fresh copy of the job, so the in-memory
newVersionIsHealthy flag was always false there and a failure after the
old container stopped removed the only running container. Keep the flag
in the cache, keyed by the deployment UUID.

Closes #12253

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-23 23:03:33 +02:00

..

Feature

fix(deploy): keep the healthy new container when a rolling update fails late

2026-10-23 23:03:33 +02:00

Fixtures

fix(previews): keep compose preview data out of production pending changes

2026-10-23 19:46:44 +02:00

Scripts

…

Support

fix(server-transfer): keep imported data exact and guard archived servers

2026-10-22 15:52:20 +02:00

Traits

…

Unit

fix(deploy): keep the healthy new container when a rolling update fails late

2026-10-23 23:03:33 +02:00

v4

feat(ui): add four-color custom theme dialog with presets and share code

2026-10-23 22:07:21 +02:00

CreatesApplication.php

…

Pest.php

…

TestCase.php

…