Release v8.0.2: dependency updates + Rust 1.91+ build fix

[keaz]

User description

Summary

• bump crate version to 8.0.2
• update direct dependencies in Cargo.toml to current compatible versions
• fix Rust 1.91+ lifetime build regression in streaming search by returning boxed streams (without adding 'static bounds)

Validation

• cargo test (unit, integration with Docker OpenDJ, pool tests, and doctests)

Closes #38

---

CodeAnt-AI Description

Release v8.0.2: dependency updates and Rust 1.91+ build fix

What Changed

• Builds now succeed on Rust 1.91+ by returning boxed, pinned streams for streaming search APIs, avoiding previous lifetime errors with pooled clients.
• Updated multiple dependencies and crate version to 8.0.2 so the library uses newer patch releases for transitive crates.
• Streaming search behavior for pooled clients no longer requires artificial external lifetimes, making pooled usage compile cleanly.

Impact

✅ Builds on Rust 1.91+
✅ Easier use with connection pools (no lifetime compile errors)
✅ Uses newer dependency releases

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

CodeAnt AI is reviewing your PR.

[codeant-ai]

Nitpicks 🔍

🔒 No security issues identified

⚡ Recommended areas for review Blocking work in Drop The StreamDropWrapper Drop implementation uses block_on to run async cleanup. That blocking call can interact poorly with executors and may impact latency. Since streams are now boxed and more widely used, this blocking behavior should be re-examined (e.g., try to use a non-blocking fallback, try_current handle + spawn, or document the blocking behavior). Executor / Send compatibility The newly boxed streams are not marked Send. On multi-threaded executors (tokio multi-thread runtime) non-Send streams cannot be .await/Spawned across threads. If consumers expect to move the stream between threads or spawn tasks that own the stream, the missing Send bound will be an issue. Decide whether the stream should be Send and add appropriate bounds (and/or use a Send-boxed stream). Performance Impact The PR boxes all streaming search results (Pin<Box<dyn Stream<...>>>). Boxing fixes the lifetime/regression but adds heap allocation and dynamic dispatch for every returned stream. For hot paths that create many streams this could add measurable overhead. Consider whether boxing is necessary in all call-sites or if a more targeted approach (e.g. returning boxed only when required) is possible.

[codeant-ai]

CodeAnt AI finished reviewing your PR.

[Iizuki]

The build was already fixed in #40. These code changes are just reintroducing the previous attempt at fixing it. They should be removed.