Skip to content

build(deps): bump the python-deps group with 7 updates - #536

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/python-deps-c5675b6cf4
Open

build(deps): bump the python-deps group with 7 updates#536
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/python-deps-c5675b6cf4

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 27, 2026

Copy link
Copy Markdown

Updates the requirements on lancedb, openai, everalgo-user-memory, everalgo-agent-memory, everalgo-knowledge, everalgo-boundary and everalgo-core to permit the latest version.
Updates lancedb to 0.40.0

Release notes

Sourced from lancedb's releases.

LanceDB v0.40.0

This stable release uses Lance 13.0.0 and is maintained on release/v0.40.

Java packaging: Use com.lancedb:lancedb-core:0.40.0. The Maven artifacts were built from release-branch commit 711deef7, which corrects version serialization in the tag's Maven POMs. The Java runtime code is unchanged.

🛠 Breaking Changes

🎉 New Features

... (truncated)

Commits
  • b1b080b Bump version: 0.40.0-beta.13 → 0.40.0
  • ec92dfc Bump version: 0.40.0-beta.12 → 0.40.0-beta.13
  • 03dd419 test: avoid tied rankings in hybrid default limit coverage
  • 1ee95c3 chore: prepare LanceDB 0.40 release with Lance 13.0.0
  • 1a02a9e test: match the RC external blob validation error
  • 0f62894 chore: validate Lance v13.0.0-rc.1
  • 4730f90 Bump version: 0.40.0-beta.11 → 0.40.0-beta.12
  • 82d3948 feat(functions): address Functions by namespace path (#4341)
  • 0a1c1a0 feat(node): accept an AbortSignal to cancel blob reads (#4350)
  • ad79112 fix(node): support LargeUtf8 and LargeBinary Arrow columns (#4287)
  • Additional commits viewable in compare view

Updates openai to 3.37.0

Release notes

Sourced from openai's releases.

v3.37.0

3.37.0 (2026-10-22)

⚠ BREAKING CHANGES

  • api: This minor release includes a breaking change to Decisions types. In Live response models, question instructions can now be a string or a list of structured text, image, or JSON parts; check isinstance(question.instructions, str) before using string operations and handle the structured form. Decisions request input types also include additional message roles and tool-history items, so update exhaustive type checks accordingly. Existing string instructions and DecisionInputMessageParam user-message inputs remain supported.

Features

  • api: expand Decisions input and question types (#4158) (1e45ad1)

Chores

  • api: preserve file and video polling helpers (#4155) (7db9d88)
  • api: preserve upload helpers and Live connection defaults (#4152) (a29dc39)
  • deps: bump astral-sh/setup-uv from 10.2.0 to 10.3.0 (#4109) (fa9a161)
Changelog

Sourced from openai's changelog.

3.37.0 (2026-10-22)

⚠ BREAKING CHANGES

  • api: This minor release includes a breaking change to Decisions types. In Live response models, question instructions can now be a string or a list of structured text, image, or JSON parts; check isinstance(question.instructions, str) before using string operations and handle the structured form. Decisions request input types also include additional message roles and tool-history items, so update exhaustive type checks accordingly. Existing string instructions and DecisionInputMessageParam user-message inputs remain supported.

Features

  • api: expand Decisions input and question types (#4158) (1e45ad1)

Chores

  • api: preserve file and video polling helpers (#4155) (7db9d88)
  • api: preserve upload helpers and Live connection defaults (#4152) (a29dc39)
  • deps: bump astral-sh/setup-uv from 10.2.0 to 10.3.0 (#4109) (fa9a161)

3.36.1 (2026-10-22)

Bug Fixes

  • api: honor per-call WebSocket query settings (#4138) (d40a5e1)
  • examples: stop microphone capture between recordings (#4143) (26e5d92)
  • validate browser calls before reading driver state (#4142) (2bfe460)

Chores

  • api: clarify service-account API key deletion (#4151) (6ed945e)

Refactors

  • prepare handwritten chunked upload runtime (#4146) (2d58e82)
  • prepare handwritten vector-store polling runtime (#4148) (7cd7028)

3.36.0 (2026-10-21)

Features

  • add Vertex AI support for the Responses API (#4139) (3e63d33)
  • api: add 30-minute cache-write usage counts (#4111) (5589146)
  • api: add compaction trigger IDs (#4122) (0e5794d)
  • api: add custom voice consent management (#4135) (de6d70d)
  • types: prepare native synchronous WebSocket option type (#4118) (90c0bac)

... (truncated)

Commits
  • e8a0fd2 release: 3.37.0 (#4154)
  • fa9a161 chore(deps): bump astral-sh/setup-uv from 10.2.0 to 10.3.0 (#4109)
  • 1e45ad1 feat(api): expand Decisions input and question types (#4158)
  • 1f76a59 ci: allow time for browser dependency installation (#4159)
  • 7db9d88 chore(api): preserve file and video polling helpers (#4155)
  • a29dc39 chore(api): preserve upload helpers and Live connection defaults (#4152)
  • 49e6757 release: 3.36.1 (#4145)
  • 6ed945e chore(api): clarify service-account API key deletion (#4151)
  • 7cd7028 refactor: prepare handwritten vector-store polling runtime (#4148)
  • d40a5e1 fix(api): honor per-call WebSocket query settings (#4138)
  • Additional commits viewable in compare view

Updates everalgo-user-memory from 0.4.0 to 0.7.0

Changelog

Sourced from everalgo-user-memory's changelog.

Changelog

All notable changes to the EverAlgo monorepo are documented here. Format follows Keep a Changelog 1.1.0. Each distribution follows its own Semantic Versioning 2.0 cadence — there is no umbrella version.

Per-distribution changelogs are the source of truth. This file is a navigation index.

Distribution status

The table tracks the current version declared in each packages/everalgo-*/pyproject.toml. All eight distributions are published to PyPI.

Distribution Version Changelog
everalgo-core 0.6.0 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-core/CHANGELOG.md
everalgo-boundary 0.4.1 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-boundary/CHANGELOG.md
everalgo-clustering 0.3.0rc2 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-clustering/CHANGELOG.md
everalgo-rank 0.5.0rc3 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-rank/CHANGELOG.md
everalgo-user-memory 0.9.0rc4 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-user-memory/CHANGELOG.md
everalgo-agent-memory 0.6.0rc3 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-agent-memory/CHANGELOG.md
everalgo-parser 0.3.0rc2 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-parser/CHANGELOG.md
everalgo-knowledge 0.3.0rc2 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-knowledge/CHANGELOG.md

[everalgo-boundary/0.4.1] - 2026-10-27

Fixes premature closure of single-message and multi-message streaming workflows by distinguishing task execution from closed status exchanges. Batch input preserves message boundaries when content contains XML delimiters or line breaks, and the prompt requests short tail evidence without changing the strict reply schema or step path. See the package changelog. Other distributions and dependency floors remain unchanged.

Release candidate — 2026-10-22 (agent-memory 0.6.0rc3)

One distribution moves to the next release candidate for one feature: optional correctness admission before agent Case extraction. AgentCaseExtractor(gate=AgentCaseGate(judge=...)) asks a host-supplied CaseJudge for the probability that the work in a closed conversation was completed correctly, admits it at >=0.70, and admits conversations above 50,000 o200k_base tokens without a judge call; an admitted Case carries case_gate provenance that routes its Skill extraction to an admitted-case variant of the success prompt. The judge is a Protocol: the host owns the provider, transport and credentials, and algo owns the question text, sizing, thresholds and probability validation. Without a gate nothing changes. No dependency floor moves; the other seven distributions have no change and keep their versions.

Distribution Version Bump
everalgo-agent-memory 0.6.0rc3 optional Case admission gate with a host-supplied judge

Detail in https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-agent-memory/CHANGELOG.md.

Commits
  • 20c8622 Merge branch 'release/user-memory-v0.7.0' into 'main'
  • 522b313 🔖 release(user-memory): 0.7.0 — profile prompt rewrite around one definition ...
  • 8675b16 Merge branch 'fix/profile-explicit-info-event-pollution' into 'main'
  • 2fb9ddf 🐛 fix(user-memory): rewrite the profile prompts around one definition of a po...
  • 6756474 Merge branch 'release/boundary-user-agent-memory' into 'main'
  • 27f400c 🔖 release(release): boundary 0.3.0 + user-memory 0.6.0 + agent-memory 0.5.0 —...
  • 305ed10 Merge branch 'fix/boundary-should-wait' into 'main'
  • 0da1697 🐛 fix(boundary)!: surface the LLM's should_wait verdict instead of discarding it
  • 0f0ae7d Merge branch 'release/core-user-memory-v0.5.0' into 'main'
  • b68b0fe 🔖 release(release): core 0.5.0 + user-memory 0.5.0 — model-written Episode.su...
  • Additional commits viewable in compare view

Updates everalgo-agent-memory from 0.4.0 to 0.5.1

Changelog

Sourced from everalgo-agent-memory's changelog.

Changelog

All notable changes to the EverAlgo monorepo are documented here. Format follows Keep a Changelog 1.1.0. Each distribution follows its own Semantic Versioning 2.0 cadence — there is no umbrella version.

Per-distribution changelogs are the source of truth. This file is a navigation index.

Distribution status

The table tracks the current version declared in each packages/everalgo-*/pyproject.toml. All eight distributions are published to PyPI.

Distribution Version Changelog
everalgo-core 0.6.0 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-core/CHANGELOG.md
everalgo-boundary 0.4.1 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-boundary/CHANGELOG.md
everalgo-clustering 0.3.0rc2 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-clustering/CHANGELOG.md
everalgo-rank 0.5.0rc3 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-rank/CHANGELOG.md
everalgo-user-memory 0.9.0rc4 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-user-memory/CHANGELOG.md
everalgo-agent-memory 0.6.0rc3 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-agent-memory/CHANGELOG.md
everalgo-parser 0.3.0rc2 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-parser/CHANGELOG.md
everalgo-knowledge 0.3.0rc2 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-knowledge/CHANGELOG.md

[everalgo-boundary/0.4.1] - 2026-10-27

Fixes premature closure of single-message and multi-message streaming workflows by distinguishing task execution from closed status exchanges. Batch input preserves message boundaries when content contains XML delimiters or line breaks, and the prompt requests short tail evidence without changing the strict reply schema or step path. See the package changelog. Other distributions and dependency floors remain unchanged.

Release candidate — 2026-10-22 (agent-memory 0.6.0rc3)

One distribution moves to the next release candidate for one feature: optional correctness admission before agent Case extraction. AgentCaseExtractor(gate=AgentCaseGate(judge=...)) asks a host-supplied CaseJudge for the probability that the work in a closed conversation was completed correctly, admits it at >=0.70, and admits conversations above 50,000 o200k_base tokens without a judge call; an admitted Case carries case_gate provenance that routes its Skill extraction to an admitted-case variant of the success prompt. The judge is a Protocol: the host owns the provider, transport and credentials, and algo owns the question text, sizing, thresholds and probability validation. Without a gate nothing changes. No dependency floor moves; the other seven distributions have no change and keep their versions.

Distribution Version Bump
everalgo-agent-memory 0.6.0rc3 optional Case admission gate with a host-supplied judge

Detail in https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-agent-memory/CHANGELOG.md.

Commits
  • 7746a87 Merge branch 'release/tokenizer-special-token-patch' into 'main'
  • 49daece 🔖 release(release): core 0.5.1 + agent-memory 0.5.1 + knowledge 0.2.1 — speci...
  • d3a3117 Merge branch 'fix/tokenizer-special-tokens' into 'main'
  • 4bb3e31 🐛 fix(core): stop tiktoken rejecting text that quotes a special token
  • d830fec Merge branch 'release/knowledge-v0.2.0-changelog' into 'main'
  • 31881a3 📝 docs(knowledge): restore Unreleased changelog section
  • dc89c78 Merge branch 'fix/knowledge-json-invalid-escape' into 'main'
  • 91b11ec 🐛 fix(knowledge): recover LLM JSON whose only defect is an invalid backslash ...
  • b1fa05a Merge branch 'release/user-memory-v0.8.0rc9' into 'main'
  • 2030d42 🔖 release(user-memory): 0.8.0rc9 — the historical pass stops re-adding supers...
  • Additional commits viewable in compare view

Updates everalgo-knowledge from 0.1.1 to 0.2.1

Changelog

Sourced from everalgo-knowledge's changelog.

Changelog

All notable changes to the EverAlgo monorepo are documented here. Format follows Keep a Changelog 1.1.0. Each distribution follows its own Semantic Versioning 2.0 cadence — there is no umbrella version.

Per-distribution changelogs are the source of truth. This file is a navigation index.

Distribution status

The table tracks the current version declared in each packages/everalgo-*/pyproject.toml. All eight distributions are published to PyPI.

Distribution Version Changelog
everalgo-core 0.6.0 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-core/CHANGELOG.md
everalgo-boundary 0.4.1 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-boundary/CHANGELOG.md
everalgo-clustering 0.3.0rc2 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-clustering/CHANGELOG.md
everalgo-rank 0.5.0rc3 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-rank/CHANGELOG.md
everalgo-user-memory 0.9.0rc4 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-user-memory/CHANGELOG.md
everalgo-agent-memory 0.6.0rc3 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-agent-memory/CHANGELOG.md
everalgo-parser 0.3.0rc2 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-parser/CHANGELOG.md
everalgo-knowledge 0.3.0rc2 https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-knowledge/CHANGELOG.md

[everalgo-boundary/0.4.1] - 2026-10-27

Fixes premature closure of single-message and multi-message streaming workflows by distinguishing task execution from closed status exchanges. Batch input preserves message boundaries when content contains XML delimiters or line breaks, and the prompt requests short tail evidence without changing the strict reply schema or step path. See the package changelog. Other distributions and dependency floors remain unchanged.

Release candidate — 2026-10-22 (agent-memory 0.6.0rc3)

One distribution moves to the next release candidate for one feature: optional correctness admission before agent Case extraction. AgentCaseExtractor(gate=AgentCaseGate(judge=...)) asks a host-supplied CaseJudge for the probability that the work in a closed conversation was completed correctly, admits it at >=0.70, and admits conversations above 50,000 o200k_base tokens without a judge call; an admitted Case carries case_gate provenance that routes its Skill extraction to an admitted-case variant of the success prompt. The judge is a Protocol: the host owns the provider, transport and credentials, and algo owns the question text, sizing, thresholds and probability validation. Without a gate nothing changes. No dependency floor moves; the other seven distributions have no change and keep their versions.

Distribution Version Bump
everalgo-agent-memory 0.6.0rc3 optional Case admission gate with a host-supplied judge

Detail in https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-agent-memory/CHANGELOG.md.

Coordinated release — 2026-10-20 (core 0.6.0, boundary 0.4.0)

Two distributions leave release candidate: everalgo-core 0.6.0rc3 and everalgo-boundary 0.4.0rc5 become 0.6.0 and 0.4.0. Core has no code change since 0.6.0rc3. Boundary's source is byte-for-byte that of 0.4.0rc5; the one change is its core floor, raised from >=0.6.0rc3 to the final >=0.6.0, so a resolver no longer picks a core release candidate for it. The other six distributions have no change and keep their versions; their core floors (>=0.6.0rc3 for clustering, knowledge, rank and user-memory, >=0.6.0rc2 for agent-memory and parser) and the boundary floor of agent-memory and user-memory (>=0.4.0rc1) are already met by these releases.

Distribution Version Bump
everalgo-core 0.6.0 0.6.0rc3 promoted unchanged
everalgo-boundary 0.4.0 0.4.0rc5 promoted unchanged; core floor >=0.6.0

Detail in https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-core/CHANGELOG.md and https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-boundary/CHANGELOG.md; the release-candidate sections below record the changes since 0.5.1 and 0.3.0.

Release candidate — 2026-10-19 (boundary 0.4.0rc5)

... (truncated)

Commits
  • 7746a87 Merge branch 'release/tokenizer-special-token-patch' into 'main'
  • 49daece 🔖 release(release): core 0.5.1 + agent-memory 0.5.1 + knowledge 0.2.1 — speci...
  • d3a3117 Merge branch 'fix/tokenizer-special-tokens' into 'main'
  • 4bb3e31 🐛 fix(core): stop tiktoken rejecting text that quotes a special token
  • d830fec Merge branch 'release/knowledge-v0.2.0-changelog' into 'main'
  • 31881a3 📝 docs(knowledge): restore Unreleased changelog section
  • dc89c78 Merge branch 'fix/knowledge-json-invalid-escape' into 'main'
  • 91b11ec 🐛 fix(knowledge): recover LLM JSON whose only defect is an invalid backslash ...
  • b1fa05a Merge branch 'release/user-memory-v0.8.0rc9' into 'main'
  • 2030d42 🔖 release(user-memory): 0.8.0rc9 — the historical pass stops re-adding supers...
  • Additional commits viewable in compare view

Updates everalgo-boundary from 0.2.1 to 0.4.0

Changelog

Sourced from everalgo-boundary's changelog.

Coordinated release — 2026-10-20 (core 0.6.0, boundary 0.4.0)

Two distributions leave release candidate: everalgo-core 0.6.0rc3 and everalgo-boundary 0.4.0rc5 become 0.6.0 and 0.4.0. Core has no code change since 0.6.0rc3. Boundary's source is byte-for-byte that of 0.4.0rc5; the one change is its core floor, raised from >=0.6.0rc3 to the final >=0.6.0, so a resolver no longer picks a core release candidate for it. The other six distributions have no change and keep their versions; their core floors (>=0.6.0rc3 for clustering, knowledge, rank and user-memory, >=0.6.0rc2 for agent-memory and parser) and the boundary floor of agent-memory and user-memory (>=0.4.0rc1) are already met by these releases.

Distribution Version Bump
everalgo-core 0.6.0 0.6.0rc3 promoted unchanged
everalgo-boundary 0.4.0 0.4.0rc5 promoted unchanged; core floor >=0.6.0

Detail in https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-core/CHANGELOG.md and https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-boundary/CHANGELOG.md; the release-candidate sections below record the changes since 0.5.1 and 0.3.0.

Release candidate — 2026-10-19 (boundary 0.4.0rc5)

One distribution moves to the next release candidate for one fix: the third batch worked example's reasoning drops a tail note the reply format does not allow, so the example matches the definition's "and nothing more". The reply contract and the BoundaryDetector interface are unchanged. No dependency floor moves; the other seven distributions have no change and keep their versions.

Distribution Version Bump
everalgo-boundary 0.4.0rc5 third batch example's reasoning ends at its split points

Detail in https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-boundary/CHANGELOG.md.

Release candidate — 2026-10-19 (boundary 0.4.0rc4)

One distribution moves to the next release candidate for a batch-prompt revision: reasoning is bounded to short topic labels with their message ranges and the split points, the cross-day split rule and the transition-phrase line are removed, and the first worked example shows a courtesy reply staying with the topic it closes. The reply contract and the BoundaryDetector interface are unchanged. No dependency floor moves; the other seven distributions have no change and keep their versions.

Distribution Version Bump
everalgo-boundary 0.4.0rc4 short-label batch reasoning, no cross-day or transition-phrase rule, courtesy-reply example

Detail in https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-boundary/CHANGELOG.md.

Release candidate — 2026-10-13 (user-memory 0.9.0rc4)

One distribution moves to the next release candidate for one fix: reflection keeps every time as the episodes wrote it. Both reflect modes used to demand a UTC label on every clock time, which contradicted episode v2.2: extraction labels only the clock times it derives itself and leaves the ones speakers quoted unlabelled, because their timezone is unknown, so merging invented a zone for exactly those times ("at 4" became "4:00 UTC"). The two time rules now add or drop no zone label. No dependency floor moves; the other seven distributions have no change and keep their rc3 or rc2 versions.

Distribution Version Bump
everalgo-user-memory 0.9.0rc4 reflect time rules keep clock times as written, adding no UTC label

Detail in https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-user-memory/CHANGELOG.md.

Coordinated release — 2026-10-13 (rc3)

Six distributions move to the next release candidate for one refactor: the <custom_instructions> block that closes a system message is now built in one place, everalgo.utils.append_custom_instructions in everalgo-core 0.6.0rc3. Five packages that take custom_instructions each kept their own copy of that logic; they call the core function instead, and a repository test fails on a copy. The rendered system message is byte-for-byte unchanged through every public entry point. One edge differs: a direct call of an everalgo-user-memory prompt module's assemble_system_prompt with an empty or blank custom_instructions now leaves the block out, as None does, where it used to emit an empty block. Because the five packages import a function that only everalgo-core 0.6.0rc3 defines, their core floor becomes >=0.6.0rc3; everalgo-agent-memory and everalgo-parser have no change and stay at 0.6.0rc2 and 0.3.0rc2.

Distribution Version Bump
everalgo-core 0.6.0rc3 new everalgo.utils.append_custom_instructions
everalgo-boundary 0.4.0rc3 calls the core function; core floor >=0.6.0rc3
everalgo-rank 0.5.0rc3 calls the core function, private _render.py removed; core floor >=0.6.0rc3

... (truncated)

Commits
  • 72cad93 Merge branch 'release/core-0.6.0-boundary-0.4.0' into 'main'
  • bd15475 🔖 release(release): everalgo-core 0.6.0 and everalgo-boundary 0.4.0 — promote...
  • 1e18d4d Merge branch 'fix/boundary-example3-reasoning' into 'main'
  • f13d917 🔖 release(boundary): everalgo-boundary 0.4.0rc5 — the third batch example say...
  • a6de61a Merge branch 'feat/boundary-example-courtesy-reply' into 'main'
  • 5829fbd 🔖 release(boundary): everalgo-boundary 0.4.0rc4 — short-label reasoning, no c...
  • 6053eb7 Merge branch 'fix/reflect-keep-quoted-clock-times' into 'main'
  • 18726ab 🔖 release(release): rc4 of everalgo-user-memory — reflect keeps clock times a...
  • 11767f1 Merge branch 'refactor/custom-instructions-helper' into 'main'
  • 8cb4167 🔖 release(release): rc3 of six distributions — one append_custom_instructions...
  • Additional commits viewable in compare view

Updates everalgo-core from 0.3.0 to 0.6.0

Changelog

Sourced from everalgo-core's changelog.

Release candidate — 2026-10-22 (agent-memory 0.6.0rc3)

One distribution moves to the next release candidate for one feature: optional correctness admission before agent Case extraction. AgentCaseExtractor(gate=AgentCaseGate(judge=...)) asks a host-supplied CaseJudge for the probability that the work in a closed conversation was completed correctly, admits it at >=0.70, and admits conversations above 50,000 o200k_base tokens without a judge call; an admitted Case carries case_gate provenance that routes its Skill extraction to an admitted-case variant of the success prompt. The judge is a Protocol: the host owns the provider, transport and credentials, and algo owns the question text, sizing, thresholds and probability validation. Without a gate nothing changes. No dependency floor moves; the other seven distributions have no change and keep their versions.

Distribution Version Bump
everalgo-agent-memory 0.6.0rc3 optional Case admission gate with a host-supplied judge

Detail in https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-agent-memory/CHANGELOG.md.

Coordinated release — 2026-10-20 (core 0.6.0, boundary 0.4.0)

Two distributions leave release candidate: everalgo-core 0.6.0rc3 and everalgo-boundary 0.4.0rc5 become 0.6.0 and 0.4.0. Core has no code change since 0.6.0rc3. Boundary's source is byte-for-byte that of 0.4.0rc5; the one change is its core floor, raised from >=0.6.0rc3 to the final >=0.6.0, so a resolver no longer picks a core release candidate for it. The other six distributions have no change and keep their versions; their core floors (>=0.6.0rc3 for clustering, knowledge, rank and user-memory, >=0.6.0rc2 for agent-memory and parser) and the boundary floor of agent-memory and user-memory (>=0.4.0rc1) are already met by these releases.

Distribution Version Bump
everalgo-core 0.6.0 0.6.0rc3 promoted unchanged
everalgo-boundary 0.4.0 0.4.0rc5 promoted unchanged; core floor >=0.6.0

Detail in https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-core/CHANGELOG.md and https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-boundary/CHANGELOG.md; the release-candidate sections below record the changes since 0.5.1 and 0.3.0.

Release candidate — 2026-10-19 (boundary 0.4.0rc5)

One distribution moves to the next release candidate for one fix: the third batch worked example's reasoning drops a tail note the reply format does not allow, so the example matches the definition's "and nothing more". The reply contract and the BoundaryDetector interface are unchanged. No dependency floor moves; the other seven distributions have no change and keep their versions.

Distribution Version Bump
everalgo-boundary 0.4.0rc5 third batch example's reasoning ends at its split points

Detail in https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-boundary/CHANGELOG.md.

Release candidate — 2026-10-19 (boundary 0.4.0rc4)

One distribution moves to the next release candidate for a batch-prompt revision: reasoning is bounded to short topic labels with their message ranges and the split points, the cross-day split rule and the transition-phrase line are removed, and the first worked example shows a courtesy reply staying with the topic it closes. The reply contract and the BoundaryDetector interface are unchanged. No dependency floor moves; the other seven distributions have no change and keep their versions.

Distribution Version Bump
everalgo-boundary 0.4.0rc4 short-label batch reasoning, no cross-day or transition-phrase rule, courtesy-reply example

Detail in https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-boundary/CHANGELOG.md.

Release candidate — 2026-10-13 (user-memory 0.9.0rc4)

One distribution moves to the next release candidate for one fix: reflection keeps every time as the episodes wrote it. Both reflect modes used to demand a UTC label on every clock time, which contradicted episode v2.2: extraction labels only the clock times it derives itself and leaves the ones speakers quoted unlabelled, because their timezone is unknown, so merging invented a zone for exactly those times ("at 4" became "4:00 UTC"). The two time rules now add or drop no zone label. No dependency floor moves; the other seven distributions have no change and keep their rc3 or rc2 versions.

Distribution Version Bump
everalgo-user-memory 0.9.0rc4 reflect time rules keep clock times as written, adding no UTC label

Detail in https://github.com/EverMind-AI/EverAlgo/blob/main/packages/everalgo-user-memory/CHANGELOG.md.

... (truncated)

Commits
  • 72cad93 Merge branch 'release/core-0.6.0-boundary-0.4.0' into 'main'
  • bd15475 🔖 release(release): everalgo-core 0.6.0 and everalgo-boundary 0.4.0 — promote...
  • 1e18d4d Merge branch 'fix/boundary-example3-reasoning' into 'main'
  • f13d917 🔖 release(boundary): everalgo-boundary 0.4.0rc5 — the third batch example say...
  • a6de61a Merge branch 'feat/boundary-example-courtesy-reply' into 'main'
  • 5829fbd 🔖 release(boundary): everalgo-boundary 0.4.0rc4 — short-label reasoning, no c...
  • 6053eb7 Merge branch 'fix/reflect-keep-quoted-clock-times' into 'main'
  • 18726ab 🔖 release(release): rc4 of everalgo-user-memory — reflect keeps clock times a...
  • 11767f1 Merge branch 'refactor/custom-instructions-helper' into 'main'
  • 8cb4167 🔖 release(release): rc3 of six distributions — one append_custom_instructions...
  • 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
  • `@dependab...

Description has been truncated

@dependabot
build(deps): bump the python-deps group with 7 updates
470daad 
Updates the requirements on [lancedb](https://github.com/lancedb/lancedb), [openai](https://github.com/openai/openai-python), [everalgo-user-memory](https://github.com/EverMind-AI/EverAlgo), [everalgo-agent-memory](https://github.com/EverMind-AI/EverAlgo), [everalgo-knowledge](https://github.com/EverMind-AI/EverAlgo), [everalgo-boundary](https://github.com/EverMind-AI/EverAlgo) and [everalgo-core](https://github.com/EverMind-AI/EverAlgo) to permit the latest version.

Updates `lancedb` to 0.40.0
- [Release notes](https://github.com/lancedb/lancedb/releases)
- [Changelog](https://github.com/lancedb/lancedb/blob/main/release_process.md)
- [Commits](lancedb/lancedb@python-v0.34.0...v0.40.0)

Updates `openai` to 3.37.0
- [Release notes](https://github.com/openai/openai-python/releases)
- [Changelog](https://github.com/openai/openai-python/blob/main/CHANGELOG.md)
- [Commits](openai/openai-python@v1.0.0...v3.37.0)

Updates `everalgo-user-memory` from 0.4.0 to 0.7.0
- [Release notes](https://github.com/EverMind-AI/EverAlgo/releases)
- [Changelog](https://github.com/EverMind-AI/EverAlgo/blob/main/CHANGELOG.md)
- [Commits](EverMind-AI/EverAlgo@everalgo-user-memory/v0.4.0...everalgo-user-memory/v0.7.0)

Updates `everalgo-agent-memory` from 0.4.0 to 0.5.1
- [Release notes](https://github.com/EverMind-AI/EverAlgo/releases)
- [Changelog](https://github.com/EverMind-AI/EverAlgo/blob/main/CHANGELOG.md)
- [Commits](EverMind-AI/EverAlgo@everalgo-agent-memory/v0.4.0...everalgo-agent-memory/v0.5.1)

Updates `everalgo-knowledge` from 0.1.1 to 0.2.1
- [Release notes](https://github.com/EverMind-AI/EverAlgo/releases)
- [Changelog](https://github.com/EverMind-AI/EverAlgo/blob/main/CHANGELOG.md)
- [Commits](EverMind-AI/EverAlgo@everalgo-knowledge/v0.1.1...everalgo-knowledge/v0.2.1)

Updates `everalgo-boundary` from 0.2.1 to 0.4.0
- [Release notes](https://github.com/EverMind-AI/EverAlgo/releases)
- [Changelog](https://github.com/EverMind-AI/EverAlgo/blob/main/CHANGELOG.md)
- [Commits](EverMind-AI/EverAlgo@everalgo-boundary/v0.2.1...everalgo-boundary/v0.4.0)

Updates `everalgo-core` from 0.3.0 to 0.6.0
- [Release notes](https://github.com/EverMind-AI/EverAlgo/releases)
- [Changelog](https://github.com/EverMind-AI/EverAlgo/blob/main/CHANGELOG.md)
- [Commits](EverMind-AI/EverAlgo@everalgo-core/v0.3.0...everalgo-core/v0.6.0)

---
updated-dependencies:
- dependency-name: lancedb
  dependency-version: 0.40.0
  dependency-type: direct:production
  dependency-group: python-deps
- dependency-name: openai
  dependency-version: 3.37.0
  dependency-type: direct:production
  dependency-group: python-deps
- dependency-name: everalgo-user-memory
  dependency-version: 0.7.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python-deps
- dependency-name: everalgo-agent-memory
  dependency-version: 0.5.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python-deps
- dependency-name: everalgo-knowledge
  dependency-version: 0.2.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python-deps
- dependency-name: everalgo-boundary
  dependency-version: 0.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python-deps
- dependency-name: everalgo-core
  dependency-version: 0.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python-deps
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Oct 27, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file python Pull requests that update python code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants