Skip to content

Releases: Xuanwo/backon

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

v1.0.0

26 Aug 09:55
v1.0.0
ba6e069
Compare
Choose a tag to compare

Upgrade

Since 1.0.0, backon Retry doesn't take a reference of builder anymore:

+ your_fn.retry(ExponentialBuilder::default()).await;
- your_fn.retry(&ExponentialBuilder::default()).await;

Since version 0.5.0, backon no longer directly depends on tokio. Instead, users can now provide their own sleep implementation.

For example:

use anyhow::Result;
use backon::ExponentialBuilder;
use backon::Retryable;
use std::future::ready;

async fn main() -> Result<()> {
    let content = fetch
        .retry(&ExponentialBuilder::default())
        .sleep(tokio::time::sleep)
        .await?;
    Ok(())
}

To maintain the same behavior as before, please enable the tokio-sleep feature.

What's Changed

Full Changelog: v0.5.0...v1.0.0

v0.5.0

22 Aug 11:07
v0.5.0
d292fae
Compare
Choose a tag to compare

Upgrade

Since version 0.5.0, backon no longer directly depends on tokio. Instead, users can now provide their own sleep implementation.

For example:

use anyhow::Result;
use backon::ExponentialBuilder;
use backon::Retryable;
use std::future::ready;

async fn main() -> Result<()> {
    let content = fetch
        .retry(&ExponentialBuilder::default())
        .sleep(tokio::time::sleep)
        .await?;
    Ok(())
}

To maintain the same behavior as before, please enable the tokio-sleep feature.

What's Changed

  • Remove duplicate example, point to examples on docs index page by @matildasmeds in #84
  • ci: Use macos-latest for test by @Xuanwo in #87
  • feat: Remove dependences on pin_project and futures_core by @Xuanwo in #86
  • docs: Add an example for sqlx by @Xuanwo in #91
  • Use wasm-compatible sleep if compiled for wasm32 by @wackazong in #92
  • feat: Allow user to provide sleeper by @Xuanwo in #93
  • Bump to version 0.5.0 by @Xuanwo in #94

New Contributors

Full Changelog: v0.4.4...v0.5.0

v0.4.4

08 Apr 03:40
v0.4.4
7e90660
Compare
Choose a tag to compare

What's Changed

  • docs: Update README by @Xuanwo in #76
  • chore(deps): update reqwest requirement from 0.11 to 0.12 by @dependabot in #78
  • feat: Add blocking retry with context support by @Xuanwo in #80
  • Bump backon to 0.4.4 by @Xuanwo in #81

Full Changelog: v0.4.3...v0.4.4

v0.4.3

08 Mar 09:26
v0.4.3
fe815a8
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.4.2...v0.4.3

v0.4.2

21 Feb 10:45
v0.4.2
a5ba69f
Compare
Choose a tag to compare

What's Changed

  • fix: Make backon work in wasm by @Xuanwo in #60
  • chore(deps): update fastrand requirement from 1.9.0 to 2.0.0 by @dependabot in #62
  • chore(deps): bump actions/checkout from 3 to 4 by @dependabot in #64
  • docs: Document tokio::time::sleep usage by @vriesk in #66
  • fix: fix with_factor assert by @wcy-fdu in #68
  • Bump to version 0.4.2 by @Xuanwo in #69

New Contributors

Full Changelog: v0.4.1...v0.4.2