Skip to content

docs(rust): sync async-openai version pin to 0.38 #660

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
amavashev merged 1 commit into from
May 16, 2026
Merged

docs(rust): sync async-openai version pin to 0.38 #660

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions how-to/integrating-cycles-with-async-openai.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,19 +25,19 @@ The same lifecycle composes against other Rust LLM clients (Anthropic, Bedrock,
```toml
[dependencies]
runcycles = "0.2"
async-openai = "0.30" # check crates.io for the current version
async-openai = { version = "0.38", default-features = false, features = ["chat-completion", "rustls"] }
tokio = { version = "1", features = ["full"] }
futures = "0.3" # for stream consumption
```

`async-openai` major versions change occasionally. The shape of the API (chat completions, usage, streaming) has been stable for several minor releases; the type paths in this guide are accurate to the 0.30.x line at publication. If you pin a different version, the names below may need a small adjustment.
`async-openai` 0.31+ splits its surface behind per-API features — the `chat-completion` feature is what makes `Client` and the chat-completion types available. The 0.30.x line bundled everything by default; if you're upgrading from there, the example uses `async_openai::types::chat::` paths (the chat types moved out of the top-level `types::` module in 0.31). The 0.30.x line also pulled `backoff` transitively, which has been replaced with `tower` in 0.31+ — worth the version bump for the cleaner dependency tree alone.

## The basic pattern: with_cycles + chat completions

```rust
use async_openai::{
Client,
types::{CreateChatCompletionRequestArgs, ChatCompletionRequestUserMessageArgs, Role},
types::chat::{CreateChatCompletionRequestArgs, ChatCompletionRequestUserMessageArgs},
};
use runcycles::{
CyclesClient, with_cycles, WithCyclesConfig,
Expand Down Expand Up @@ -153,7 +153,7 @@ OpenAI's streaming endpoint emits a final `usage` chunk only when `stream_option
```rust
use async_openai::{
Client,
types::{
types::chat::{
CreateChatCompletionRequestArgs,
ChatCompletionRequestUserMessageArgs,
ChatCompletionStreamOptions,
Expand Down Expand Up @@ -254,7 +254,7 @@ For flows that need to act on the typed `OpenAIError`, use `ReservationGuard` an
use async_openai::{
Client,
error::OpenAIError,
types::{CreateChatCompletionRequestArgs, ChatCompletionRequestUserMessageArgs},
types::chat::{CreateChatCompletionRequestArgs, ChatCompletionRequestUserMessageArgs},
};
use runcycles::{
CyclesClient, Error as CyclesError,
Expand Down