Skip to content

Releases: Xuanwo/backon

v1.5.2

30 Jul 09:45
v1.5.2
db212c0
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.5.1...v1.5.2

v1.5.1

29 May 07:33
v1.5.1
2413c8f
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.5.0...v1.5.1

v1.5.0

09 Apr 09:17
v1.5.0
38acd5d
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.4.1...v1.5.0

v1.4.1

19 Mar 09:05
v1.4.1
19cb641
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.4.0...v1.4.1

v1.4.0

18 Feb 10:13
v1.4.0
3d3352b
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.3.0...v1.4.0

v1.3.0

22 Nov 06:24
v1.3.0
893ffca
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.2.0...v1.3.0

v1.2.0

02 Sep 05:24
v1.2.0
50ce185
Compare
Choose a tag to compare
  • backon is now available under no_std.
  • backon now supports use users own blocking sleeper too.
  • backon now raises build time error if sleeper not provided.

What's Changed

  • fix: NoopSleeper should implement default by @Xuanwo in #135
  • fix: compile to fail when using DefaultSleeper with no features enabled by @bdbai in #136
  • docs: Polish MaybeSleeper names by @Xuanwo in #137
  • feat: Add blocking sleeper for blocking retry by @Xuanwo in #138
  • Add no_std flag, hide blocking retrys behind std flag by @adrian-kong in #125
  • Bump to version 1.2.0 by @Xuanwo in #139

New Contributors

Full Changelog: v1.1.0...v1.2.0

v1.1.0

29 Aug 17:56
v1.1.0
86298fb
Compare
Choose a tag to compare

A Letter to BackON Users

Hello everyone,

Thank you very much for using BackON!

Before releasing version 1.0.0, I thought it would be better to let users choose their own sleeper implementations, so I didn't enable them by default. However, many users encountered runtime panics. I apologize for not finding a solution that meets all requirements simultaneously: no API breaks, allowing sleeper passing at runtime, and no extra cost.

So in version 1.1.0, I have added tokio-sleeper and gloo-timers-sleep to the default feature. This change will make BackON behave like version 0.4.4, allowing users to upgrade without adding new features. Additionally, I have moved the panic to occur earlier during the poll feature instead of during the sleep call. This makes it easier to catch issues during development rather than at runtime. Furthermore, we will only panic during the debug profile and do nothing in the release profile. This should protect users from panics even in the worst-case scenarios.

Please let me know if you have better solutions! Thanks in advance!

Xuanwo

What's Changed

  • docs: Polish display on the first page of lib.rs by @Xuanwo in #122
  • chore: Make backon a workspace by @Xuanwo in #124
  • docs: Add section for sleeper by @Xuanwo in #130
  • docs: Add sleep in README by @Xuanwo in #131
  • refactor: Enable default features to avoid unexpected panic by @Xuanwo in #132
  • backon: Bump to version 1.1.0 by @Xuanwo in #133

Full Changelog: v1.0.2...v1.1.0

v1.0.2

27 Aug 03:24
v1.0.2
d217a58
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.0.1...v1.0.2

v1.0.1

26 Aug 12:56
v1.0.1
f2a9062
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.0.0...v1.0.1