Skip to content

Releases: djc/bb8

v0.8.2

01 Feb 13:37
@djc djc
v0.8.2
Compare
Choose a tag to compare

What's Changed

  • Bump MSRV to 1.63 for tokio 1.30 by @djc in #173
  • Switched to Into<Option> for parameters in Builder by @fpagliughi in #185
  • Use Notify to coordinate waiters by @djc in #186

Full Changelog: v0.8.1...v0.8.2

v0.8.1

01 Feb 13:36
@djc djc
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.8.0...v0.8.1

v0.8.0

01 Feb 13:36
@djc djc
Compare
Choose a tag to compare

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

01 Feb 13:35
@djc djc
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.7.0...v0.7.1

0.7.0

27 Dec 13:35
@djc djc
Compare
Choose a tag to compare

This release updates tokio to 1.0. Additionally, it contains one additional feature:

  • Allow customization of connections after connecting (#89, thanks to @agersant)

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

27 Dec 13:33
@djc djc
Compare
Choose a tag to compare

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

27 Dec 13:33
@djc djc
Compare
Choose a tag to compare

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

16 Nov 09:01
@djc djc
Compare
Choose a tag to compare

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 on parking_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

15 Nov 22:03
@djc djc
Compare
Choose a tag to compare

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 ergonomic get() method

Other changes:

  • Switch to blocking parking_lot::Mutex instead of tokio's async Mutex (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

17 Jan 21:24
@djc djc
Compare
Choose a tag to compare

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.