Releases: djc/bb8
v0.8.2
v0.8.1
What's Changed
- Minor lints by @nyurik in #126
- UUID 1 for bb8 by @ChristianBeilschmidt in #128
- Bump to 2021 edition & inline formats by @nyurik in #125
- Set MSRV to 1.58 for now by @djc in #134
- Some minor lints by @nyurik in #132
- Fix readme example by @crsov in #135
- docs: add bb8-arangodb to readme by @gabor-boros in #136
- Test MSRV without redis by @djc in #138
- document: add bb8-redis-cluster by @0xWOF in #140
- Add option to retry connection creation, on by default by @levkk in #149
- bb8: Make parking_lot an optional feature enabled by default by @r-ml in #152
- Add LIFO option for getting pool resources by @zainkabani in #162
- Forward error to waiter before sinking by @couchand in #153
- Fix PoolInternals QueueStrategy default by @zainkabani in #163
- Fix configuration of queue strategy by @zainkabani in #165
Full Changelog: v0.8.0...v0.8.1
v0.8.0
What's Changed
- Restore ManageConnection::is_valid original signature by @arnodb in #116
- Update parking_lot requirement from 0.11 to 0.12 by @dependabot in #119
Full Changelog: v0.7.1...v0.8.0
v0.7.1
What's Changed
- Update README.md by @vkill in #101
- Upgrade to GitHub-native Dependabot by @dependabot-preview in #106
- Add
Pool::get_owned
by @davidpdrsn in #107
Full Changelog: v0.7.0...v0.7.1
0.7.0
This release updates tokio to 1.0. Additionally, it contains one additional feature:
I simultaneously published bb8-postgres 0.7.0 and bb8-redis 0.8.0. This branch is most likely to get bug fixes and additional features. The 0.5.x branch (tokio 0.2) and 0.6.x branch (tokio 0.3) will probably get less maintenance, depending on the uptake of tokio 1.
0.6.2
This is a bug fix release for the 0.6.x line (based on tokio 0.3). It fixes an issue where pools configured with a maximum size could get stuck in case futures were cancelled before completion. Thanks to @lassipulkkinen for reporting the issue (in #67) and creating a minimal reproduction which led me to the fix in #91.
0.5.2
This is a bug fix release for the 0.5.x line (based on tokio 0.2). It fixes an issue where pools configured with a maximum size could get stuck in case futures were cancelled before completion. Thanks to @lassipulkkinen for reporting the issue (in #67) and creating a minimal reproduction which led me to the fix in #91.
0.6.0
Hot on the heels of yesterday's 0.5.0 release, I've just released 0.6.0. These are the only functional changes:
- Update to tokio 0.3
- Enable tokio's
parking_lot
feature, since bb8 depends onparking_lot
anyway
For now, there is no bb8-redis 0.6 release, since there is no tokio 0.3-compatible version of the redis crate yet.
As a reminder, depending on the uptake of tokio 0.3.0 in the ecosystem, I will maintain both of these releases for a while; most features and bug fixes, for the foreseeable future, will be made against both branches.
0.5.0
After 7 months, there is finally a new release of bb8, the fully-featured connection pool for (tokio-based) async connections. This release took a while due to issues with hanging connections (described in #67), where some recent fixes appear to have solved the reported issues. While this release depends on tokio 0.2, I will release a 0.6 set of releases soon which relies on tokio 0.3 instead (update: released). Maintenance of the 0.5 branch will continue for a while, depending on the uptake of tokio 0.3 in the ecosystem.
Breaking changes:
ConnectionManager::is_valid()
now takes a&mut PooledConnection<'_, M::Connection>
- The
run()
method was removed in favor of the more ergonomicget()
method
Other changes:
- Switch to blocking
parking_lot::Mutex
instead of tokio's asyncMutex
(fixes #74) - Add basic documentation (#62, thanks to @pksunkara)
- Reduced dependencies
- bb8-redis: disable default features in redis dependency (#77, thanks to @x04)
- The
State
type became non-exhaustive - The internal structure has been substantially reworked to make it easier to reason about
0.4.0
bb8 is an r2d2-like connection pooling solution for the async/await world. This is the first release from a new maintainer: since @khuey doesn't have much time, @djc has become the primary maintainer.
- Migrate to tokio 0.2,
std::future::Future
and async/await - Upgrade to tokio-postgres 0.5 and redis 0.15
- Add a guard-based
get()
API (thanks to @elpiel) - Retry connection establishment on failure (thanks to @bbigras for contributing a test case)
Any feedback is welcome, please file any issues you may have including comments on (lack of) documentation, example code that would help you work with this projects, and of course any bugs.