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
Copy file name to clipboardExpand all lines: readme.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,10 @@ Please see the [project documentation](https://socketry.github.io/async-containe
26
26
27
27
Please see the [project releases](https://socketry.github.io/async-container/releases/index) for all releases.
28
28
29
+
### v0.27.5
30
+
31
+
- Make the child handling more robust in the face of exceptions.
32
+
29
33
### v0.27.4
30
34
31
35
- Fix race condition where `wait_for` could modify `@running` while it was being iterated over (`each_value`) during health checks.
@@ -64,10 +68,6 @@ Please see the [project releases](https://socketry.github.io/async-container/rel
64
68
65
69
-[Add support for `NOTIFY_LOG` for Kubernetes readiness probes.](https://socketry.github.io/async-container/releases/index#add-support-for-notify_log-for-kubernetes-readiness-probes.)
66
70
67
-
### v0.21.0
68
-
69
-
- Use `SIGKILL`/`Thread#kill` when the health check fails. In some cases, `SIGTERM` may not be sufficient to terminate a process because the signal can be ignored or the process may be in an uninterruptible state.
0 commit comments