From 4707c79838f1b6ed826a0b218711f44e0756d621 Mon Sep 17 00:00:00 2001 From: Vinicius Mignot Date: Mon, 14 Nov 2022 16:12:29 -0300 Subject: [PATCH] docs(README): added 1.5.2 and 1.5.3 releases --- README.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/README.md b/README.md index 49842e29..c468fe02 100644 --- a/README.md +++ b/README.md @@ -144,6 +144,24 @@ Versioning is strictly based on [Semantic Versioning](https://semver.org/) * fix: do not call on the module table, but use a method for locks. Also in [#57](https://github.com/Kong/lua-resty-healthcheck/pull/57) +### 1.5.3 (14-Nov-2022) + +* Fix: avoid raising worker events for new targets that were marked for delayed + removal, i.e. targets that already exist in memory only need the removal flag + cleared when added back. [#121](https://github.com/Kong/lua-resty-healthcheck/pull/121) + +### 1.5.2 (07-Jul-2022) + +* Better handling of `resty.lock` failure modes, adding more checks to ensure the + lock is held before running critical code, and improving the decision whether a + function should be retried after a timeout trying to acquire a lock. + [#113](https://github.com/Kong/lua-resty-healthcheck/pull/113) +* Increased logging for locked function failures. + [#114](https://github.com/Kong/lua-resty-healthcheck/pull/114) +* The cleanup frequency of deleted targets was lowered, cutting the number of + created locks in a short period. + [#116](https://github.com/Kong/lua-resty-healthcheck/pull/116) + ### 1.5.1 (23-Mar-2022) * Fix: avoid breaking active health checks when adding or removing targets.