Releases: siderolabs/go-retry
Releases · siderolabs/go-retry
v0.3.3
go-retry 0.3.3 (2023-10-19)
Welcome to the v0.3.3 release of go-retry!
Please try out the release binaries and report any issues at
https://github.com/siderolabs/go-retry/issues.
Contributors
- Andrey Smirnov
- Alexey Palazhchenko
- Andrey Smirnov
- Andrey Smirnov
- Andrey Smirnov
Changes
10 commits
23b6fc2
fix: provider modern error unwrapping6d45449
chore: rekres, renamec78cc95
fix: implementerrors.Is
for all errors in the set7885e16
feat: add ExpectedErrorf3d83f61
feat: deprecate UnexpectedErrorb9dc1a9
feat: add support forcontext.Context
in Retry8c63d29
fix: correctly implement error interfaces on wrapped errors752f081
feat: add an option to log errors being retried073067b
feat: copy initial version from talos-systems/talosc7968c5
Initial commit
Changes since v0.3.2
Dependency Changes
This release has no dependency changes
v0.3.2
go-retry 0.3.2 (2022-11-01)
Welcome to the v0.3.2 release of go-retry!
Please try out the release binaries and report any issues at
https://github.com/siderolabs/go-retry/issues.
Contributors
- Andrey Smirnov
- Alexey Palazhchenko
- Andrey Smirnov
- Andrey Smirnov
Changes
9 commits
6d45449
chore: rekres, renamec78cc95
fix: implementerrors.Is
for all errors in the set7885e16
feat: add ExpectedErrorf3d83f61
feat: deprecate UnexpectedErrorb9dc1a9
feat: add support forcontext.Context
in Retry8c63d29
fix: correctly implement error interfaces on wrapped errors752f081
feat: add an option to log errors being retried073067b
feat: copy initial version from talos-systems/talosc7968c5
Initial commit
Changes since v0.3.1
Dependency Changes
This release has no dependency changes
v0.3.1
fix: implement `errors.Is` for all errors in the set Previously it matched only a single error if the set consists of a single error. But the retry might fail many times on some expected error followed by unexpected error which we want to test for with 'errors.Is'. Signed-off-by: Andrey Smirnov <smirnov.andrey@gmail.com>
v0.3.0
v0.2.0
fix: correctly implement error interfaces on wrapped errors There were two problems: * `ExpectedError` and `UnexpectedError` should unwrap themselves * `ErrorSet` should support equivalency check when there's a single error inside. This fixes the scenario of matching an error from a retry loop (in case if just a single error was encountered). Signed-off-by: Andrey Smirnov <smirnov.andrey@gmail.com>