What crewAIInc/crewAI shipped
Written by FoxPlug from the repository's own releases; not affiliated with CrewAI. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/crewAIInc/crewAI; CrewAI did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of October 5, 2026
What shipped
- Read and write locks now keep ownership when acquisition is interrupted, stopping the reader count from dropping below zero. Pull request #7944
- SQLite flow initialization contention fixed so concurrent flow persistence setup no longer fails on locks. Pull request #7821
- A start step can now re-run on the events it listens to instead of being filtered out at runtime. Pull request #7922
- Crewai eval --models reports cost and time per run rather than summed over all runs, and stops repeating progress lines. Pull request #7965
- Evaluations now record why they stopped before a verdict, so presses that never became an evaluation have a cause. Pull request #7963
- The run app records what a Deploy press met before an attempt, including the login prompt. Pull request #7964
- Documentation site chunks keep their source URL so source attribution no longer reads as unknown. Pull request #7951
- Log-tasks-outputs prints the actual task output line instead of only the expected output. Pull request #7936
Why it matters
This week the release line moved through 1.15.24 to 1.15.27 with fixes that touch everyday work: locks that no longer misrelease, flows whose start steps honour their listeners, and evaluations that explain the gap between pressing a command and getting a verdict. Two new providers, deepinfra and OpenCLIP device options, widen what you can route and embed with, while security bumps clear flagged dependency versions. The result is quieter runs and less guesswork when something does not start.
Changelog entry
- Release 1.15.27 with OpenCLIP device options, deepinfra provider, evaluation stop reasons, Deploy encounter recording, and per-run cost and time in crewai eval --models. Release
- Fixed rwlock ownership being released when acquisition is interrupted, which could drop the reader count below zero. Pull request #7944
- Fixed SQLite flow initialization contention and concurrent flow module import races. Pull request #7821
- Start steps now re-run on the events they listen to. Pull request #7922
- Crewai eval --models now shows cost and time per run and no longer repeats progress lines. Pull request #7965
- Evaluations now record why they stopped before reaching a verdict. Pull request #7963
- The run app now records what the Deploy command met before an attempt, including the login prompt. Pull request #7964
- Documentation site loader now preserves the source URL for source attribution. Pull request #7951
- Crewai log-tasks-outputs now prints the actual output alongside the expected output. Pull request #7936
- Raised dependency floors for docling, fsspec, multidict, pymongo, and snowflake to clear pip-audit advisories. Pull request #7916
Week of September 28, 2026
What shipped
- Flows can now coordinate jobs across conversational turns while retaining typed job state and stage outputs even when later stages fail. Pull request #7864
- Crewai eval gains --models flag to compare model performance on deployed crews and flows, and
llm_overlaynow swaps models in addition to roles. Pull request #7811 - Human feedback step in declarative flows now exposes reviewer feedback in outputs so downstream steps can read it. Pull request #7850
- Crewai eval now exits with code 1 when goal gate fails and instructs users to log in when no traces were collected unattended. Pull request #7806
- Expired trace grants no longer cause crew runs to fail; crews now run untraced when authentication lapses instead of blocking execution. Pull request #7812
- Context window limits for language models are now centralized and maintained across LiteLLM and native providers. Pull request #7796
- Tracing usage metrics (
ephemeral_sentandauthenticated_sent) are now properly reported from the grant exporter. Pull request #7810 - Tool and task outputs in exported spans are now kept whole instead of being truncated or corrupted. Pull request #7833
- Pypdf dependency bumped to 6.19.0 to clear eight security advisories from pip-audit. Pull request #7851
- Litellm bumped to 1.88.6 to address authenticated SSRF and credential exfiltration vulnerability. Pull request #7835
Why it matters
This week brings job coordination across conversational flows, model evaluation tooling for comparing performance, and fixes to human feedback integration and trace reporting. Stability improvements ensure crews run untraced when authentication expires rather than failing, and security updates address vulnerabilities in pypdf and litellm.
Changelog entry
- Experimental job lifecycle and runner for Flow background work across conversational turns with retained typed job state Pull request #7864
- Crewai eval --models flag and
llm_overlaynow swap models in addition to roles for evaluation workflows Pull request #7811 - Human_feedback step with emit now exposes reviewer feedback in outputs for downstream flow steps Pull request #7850
- Crewai eval exits with code 1 on goal gate failure and prompts login when traces unavailable Pull request #7806
- Expired trace grants allow crew execution to continue untraced instead of failing immediately Pull request #7812
- Centralized context window catalog for LiteLLM and native provider models Pull request #7796
- Tracing usage metrics properly emitted from grant exporter Pull request #7810
- Tool and task outputs preserved whole in exported tracing spans Pull request #7833
- Message summarization refactored into SummarizeMessages class Pull request #7815
- Pypdf upgraded to 6.19.0 clearing eight security advisories Pull request #7851
- Litellm upgraded to 1.88.6 for authenticated SSRF vulnerability fix Pull request #7835
V1.15.23: Job coordination in conversational flows, crewai eval --models for comparing model performance, human feedback in flow outputs, and tracing fixes. Security updates to pypdf and litellm.
V1.15.23 ships job coordination across conversational flow turns with retained typed state, crewai eval --models for comparing model performance on deployed systems, and human feedback integration in declarative flows. Stability improvements let crews run untraced when authentication lapses, span exports preserve complete tool outputs, and context windows are centralized across model providers. Security updates address pypdf and litellm vulnerabilities.
Week of September 21, 2026
What shipped
- Provider throttles now retry automatically inside LLM client calls with exponential backoff, without consuming agent retries or iteration counts. Pull request #7677
- New crewai eval command evaluates the last traced run through the evaluation service, or a specific run by ID. Pull request #7649
- Traced runs are now recorded to.crewai/last_run.json for evaluation instead of printing the execution ID. Pull request #7648
- Bedrock provider falls back to synchronous calls in a worker thread when the async SDK is unavailable. Pull request #7680
- CLI crew wizard now prioritizes commonly used Platform integrations like Gmail and WhatsApp. Pull request #7573
- Generated AGENTS.md now documents Platform tool discovery and how to use tools in Python or JSON. Pull request #7581
- Security policy now includes private vulnerability reporting on the repository and a security@crewai.com contact. Pull request #7717
- SeleniumScrapingTool now keeps the browser window open for reuse across multiple calls to the same instance. Pull request #7663
- S3ReaderTool now properly closes response bodies to release HTTP resources. Pull request #7647
Why it matters
Evaluation is now integrated into the CLI workflow, making it easier to assess crew performance. Provider resilience improvements handle transient failures gracefully. Security and resource management fixes ensure reliability and proper cleanup.
Changelog entry
- Fix(llm): retry throttled provider calls with bounded exponential backoff Pull request #7677
- Fix(bedrock): fall back to sync calls when aiobotocore is unavailable Pull request #7680
- Feat(cli): prioritize popular platform integrations in crew wizard Pull request #7573
- Feat(cli): new crewai eval command to evaluate last traced run or specific runs Pull request #7649
- Feat(tracing): record last traced run to.crewai/last_run.json Pull request #7648
- Docs(cli): document platform tool discovery in generated AGENTS.md Pull request #7581
- Fix(tools): keep SeleniumScrapingTool browser window open for reuse Pull request #7663
- Fix(tools): close S3ReaderTool response bodies to release resources Pull request #7647
- Security: add private vulnerability reporting and security contact Pull request #7717
This week: automated retry logic for provider throttles, native evaluation through crewai eval, Bedrock fallback support, and better resource management across tools.
CrewAI shipped several reliability and usability improvements this week. Throttled provider calls now retry automatically without affecting agent iteration counts. The new crewai eval command lets you evaluate your last traced run directly from the CLI. Bedrock provider calls gracefully fall back to sync when async is unavailable. Plus fixes for resource cleanup in S3 operations and browser reuse in Selenium scraping.