NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io · #920 most downloaded on crates.io
Make retry like a built-in feature provided by Rust.
Last release 11 months ago
18 Oct 2025
Ships fairly regularly
a new release about every 2 months
Some releases are documented
notes for 10 of 25 stable releases
Nothing withdrawn
no release was ever pulled
4 years old
25 releases · first in 2022
One column per quarter.
chore(deps): bump actions/checkout from 4 to 5 by @dependabot [bot] in #209
Full Changelog: v1.5.2...v1.6.0
docs: Add CLAUDE.md in repo by @Xuanwo in #202
docs: add wasm32 demo by @XmchxUp in #196
Full Changelog: v1.5.0...v1.5.1
chore: Format code by @Xuanwo in #191
Full Changelog: v1.4.1...v1.5.0
jitter: Make jitter range to current_delay instead of min_delay by @DanielShaulov in #184
Full Changelog: v1.4.0...v1.4.1
chore: Remove unnecessary optional feature selectors by @wackazong in #167
futures-timer by @NumberFour8 in #154Full Changelog: v1.3.0...v1.4.0
refactor: Remove the Debug requirement of Backoff by @Xuanwo in #141
adaptable by @Xuanwo in #155with_max_times by @shikhar in #161Full Changelog: v1.2.0...v1.3.0
backon is now available under no_std .
no_std.Full Changelog: v1.1.0...v1.2.0
Thank you very much for using BackON!
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
Full Changelog: v1.0.2...v1.1.0
Nothing published for this version
Nothing published for this version
The first release of backon-macros , enjoy!
The first release of backon-macros, enjoy!
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →