chore(deps): bump cognee from 0.2.0 to 1.5.0 in the pip group across 1 directory

[dependabot]

Bumps the pip group with 1 update in the /evals/old/hotpot_qa_24_2025/src directory: cognee.

Updates cognee from 0.2.0 to 1.5.0

Release notes

Sourced from cognee's releases.

v1.5.0 — Large-scale migration & graph reliability

Release Date: 2026-08-15 Changes: v1.5.0.dev2 → main

Pull Requests: #4477, #4504, #4505

---

Summary

This release focuses on making large-scale dataset migrations reliable and faster, with many fixes and performance improvements to the Ladybug graph adapter and the migration pipeline. It also adds community plugin documentation, better LLM tuning options (temperature and seed), and CI/performance tests that validate production-shaped migrations at scale.

Highlights

• Large-scale migration validation: new release-test CI that seeds a production-shaped two-dataset system and runs the full migration chain to verify fork-splitting and rekey operations.
• Ladybug (graph adapter) stability and speedups: set-based fork re-key, chunked queries, batched rekey/restore, and fixes that make graph migrations more reliable and faster.
• Community plugins and migration docs: new cognee-community skill documentation and a tutorial for migrating from Letta/MemGPT and Zep to Cognee.
• LLM tuning and reproducibility: plumbed LLM_TEMPERATURE and added LLM_SEED support for reproducible outputs when the provider supports seeds.
• Windows support and observability hardening: ship OpenSSL for Windows to avoid TLS issues with Ladybug and batch OTLP log export while honoring tracing-off switches.

Breaking Changes

• No user-facing breaking changes in this release. Migration behavior was hardened and tested more aggressively, but there are no required changes to existing user configuration or APIs.

New Features

• Large-scale migration release test: A CI workflow seeds a production-shaped mock system (two datasets) using the pinned legacy Cognee, runs the complete migration chain on it, and verifies dataset-scoping splits and rekey_fork_document_ids. What this does: automates heavy migration validation so releases are verified against production-like data. Why it matters: catches data-migration problems before they reach users and reduces risk for upgrades.
• cognee-community documentation (new skill): A new guide that explains how to use and contribute community-maintained plugins (database adapters, connectors, and tasks). What this does: shows how to install, register, and use community packages such as Qdrant, Milvus, Slack/Gmail connectors, and more. Why it matters: makes it easier to extend Cognee with third-party adapters and connectors while avoiding common configuration pitfalls.
• Migration tutorial from Letta/MemGPT and Zep: A step-by-step migration guide and example dataset dumps to help move data into Cognee. What this does: provides concrete instructions and sample files to migrate from popular alternative systems. Why it matters: lowers the barrier to move existing memories into Cognee without manual export/import guesswork.
• LLM temperature and seed controls: Support for an LLM_TEMPERATURE environment setting (controls sampling temperature) and a new LLM_SEED setting (sampling seed for reproducible outputs when supported by the provider). What this does: sends temperature and optional seed with every LLM call when set. Why it matters: gives users control over randomness and reproducibility of LLM outputs across runs.

Improvements

• Set-based fork re-key on Ladybug: Reworked the re-key algorithm to operate on sets rather than single-item operations. What this does: reduces the number of database operations during dataset fork re-keying. Why it matters: significantly improves speed and reliability when splitting or rekeying large graphs.
• Batched migration re-embed and rekey restore calls: Vector re-embed and rekey restore work in batches instead of per-item calls. What this does: reduces load on embedding services and the database during migrations. Why it matters: lowers migration time and external API pressure for large datasets.
• Chunked edge-identity queries and write chunking tests: Queries that enumerate edge identity are now chunked and tests strengthened for write-chunking behavior. What this does: avoids oversized queries and makes large write operations safer. Why it matters: prevents timeouts and failures when performing large graph writes or rekeys.
• Trace and logging improvements: Batch OTLP log export and honor the tracing-off switch so tracing and log exports respect configuration. What this does: reduces tracing/logging overhead and prevents spurious network usage when tracing is disabled. Why it matters: improves observability performance and respects user configuration.
• CI and performance harness: Added a nightly 100k-node/-edge 'War and Peace' large-mock performance benchmark and adjusted release-test sizing and permutations. What this does: runs a production-scale stress benchmark in CI and matrices migration tests across adapter pairs. Why it matters: catches scale regressions early and validates migrations across different backend combinations.

Performance

• Faster rekeying and migration: Set-based fork re-key and batched re-embed calls reduce total migration time on large graphs (practical impact: lower wall-clock migration duration and fewer database round-trips).
• Reduced query pressure: Chunking edge-identity queries and batching rekey/restore operations reduce peak DB load and likelihood of timeouts during large operations.
• Nightly large-scale benchmark: The new 100k-node/edge mock benchmark surfaces performance regressions on production-shaped workloads so real regressions are detected earlier.

Security

• Windows OpenSSL bundled for Ladybug: The release supplies OpenSSL for Windows to avoid TLS/SSL failures when Ladybug is used on Windows. What this does: ensures secure connections work reliably on Windows hosts running the Ladybug adapter. Why it matters: avoids connectivity failures and potential insecure fallbacks on Windows deployments.

... (truncated)

Commits

• 2169926 Release v1.5.0 (#4517)
• b173cf0 test: Add large-scale migration release test (COG-6112) (#4501)
• 63e61f6 perf: Set-based fork re-key on Ladybug (COG-6185) (#4514)
• 80a23a9 Delete cognee/tests/unit/modules/migrations/test_ladybug_migration_fast_paths.py
• f4bf02f chore: set proper v1.5.0 version (#4516)
• 2bdd6a7 chore: set proper v1.5.0 version
• da14fa5 Merge branch 'dev' into perf/COG-6185-ladybug-migration-speed
• 4eb0735 fix: Supply ladybug's OpenSSL on Windows (COG-6185) (#4513)
• 623d0a5 perf: Set-based fork re-key on Ladybug (COG-6185)
• d0d5514 test: Temporarily run migration compat on postgres only
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.