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: CHANGELOG.md
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,12 @@
1
-
## v0.10.0
2
-
3
-
- Feature: New ObtainMulti method to acquire multiple locks atomically [#70](https://github.com/bsm/redislock/pull/70)
1
+
## Unreleased
2
+
3
+
- Feature: New ObtainMulti method to acquire multiple locks atomically [#70](https://github.com/bsm/redislock/pull/70)
4
+
- Feature: `Lock.Refresh` now accepts an `Options.RetryStrategy` and retries transient redis errors.
5
+
- Fix: a lost lock (refresh against a key whose value no longer matches) now returns `ErrNotObtained` immediately instead of being silently retried by the retry loop.
6
+
- Fix: `withRetry` surfaces the last transient error when retries are exhausted, instead of masking it as `ErrNotObtained`.
7
+
- Fix: when retries are interrupted by a cancelled context, return `errors.Join(ErrNotObtained, ctx.Err())` (or the last transient error joined with `ctx.Err()`) so callers can match on both with `errors.Is`.
8
+
- Docs: clarify `ExponentialBackoff` formula and the behaviour of its `min`/`max` arguments (first wait is 4ms; pass `min >= 16ms` for a sensible floor, non-zero `max` to cap growth).
9
+
- Chore: bump `go-redis/v9` to v9.19.0 and raise minimum Go to 1.25 [#86](https://github.com/bsm/redislock/pull/86).
0 commit comments