Skip to content

version: witan-council 0.46.0 - #578

Merged
blarghmatey merged 2 commits into
mainfrom
version-witan-council-0.46.0
Nov 2, 2026
Merged

blarghmatey merged 2 commits into
mainfrom
version-witan-council-0.46.0

Conversation

@blarghmatey

Copy link
Copy Markdown
Member

What are the relevant tickets?

Releases #576 and #577. witan tasks tk-recall-takes-minutes-on-the-deployed-witan-media-635dbb and tk-witan-memories-are-written-but-rarely-read-nothi-70e74d.

Description (What does it do?)

This releases witan-council 0.46.0. Merging it publishes to PyPI, because publish-witan.yml runs when this pyproject.toml version line changes. The diff is just bump witan-council minor: version, uv.lock, and the fragments collected into CHANGELOG.md.

It ships batched recall, the content budget on recall and memory_search, and memories on a first task_claim. It also ships three earlier changes that were waiting for a release: ui_url on tasks and projects (#560), --target addressing for omnigraph 0.14 (#564), and the remote merge export over HTTP.

The omnigraph pin stays at 0.13. #573 is not in this release, and the 0.14 paths here only apply when a 0.14 binary is present. The floor stays witan-core>=0.48, and 0.49.0 is on PyPI. witan-code and witan-core have fragments pending too, and those are left out because neither package changed for this work.

How can this be tested?

  • just check-versions reports all 5 packages consistent.
  • After merge, confirm publish-witan.yml succeeded and witan-council 0.46.0 is on PyPI.
  • Deployed effect, once the new image is running: repeat the recall A/B from the task and read duration_ms with {namespace="witan", container="mcp"} |= "mcp.tool_call" | json | tool="recall", and confirm witan.memory.surfaced lines appear after a first claim.

https://claude.ai/code/session_01FGZebE13gZEF6CLzyqkk9s

A newer local uv rewrote the lockfile's revision during the bump, which is
unrelated to the release.

Claude-Session: https://claude.ai/code/session_01FGZebE13gZEF6CLzyqkk9s
Copilot AI balanced review requested due to automatic review settings November 2, 2026 19:22

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues were identified for the release metadata and documentation update.

No open issues 🎉

What changed in this PR

Prepares witan-council 0.46.0 for publication, packaging previously merged memory retrieval, task-context, UI-link, and transport improvements. This PR changes release metadata and documentation, not runtime code.

Changes:

  • Updates the package version, bump configuration, and lockfile to 0.46.0.
  • Collects five changelog fragments into the release notes and removes the consumed files.
  • Leaves the omnigraph pin and other packages’ releases unchanged.
File Description
uv.lock Records witan-council version 0.46.0.
mcp/​servers/​witan/​pyproject.toml Updates package and bump configuration versions.
mcp/​servers/​witan/​CHANGELOG.md Adds consolidated release notes for 0.46.0.
mcp/​servers/​witan/​changelog.d/​20261102_163000_tmacey_surface_memories.md Removes the collected task-memory fragment.
mcp/​servers/​witan/​changelog.d/​20261102_160000_tmacey_recall_round_trips.md Removes the collected recall-performance and content-budget fragment.
mcp/​servers/​witan/​changelog.d/​20261028_113155_blarghmatey_agent_ab5f9dccfa896b575.md Removes the collected remote-merge export fragment.
mcp/​servers/​witan/​changelog.d/​20261028_104107_blarghmatey_omnigraph_014_target.md Removes the collected omnigraph addressing fragment.
mcp/​servers/​witan/​changelog.d/​20261028_083000_chudzick_ui_url.md Removes the collected UI-link fragment.

Review effort: Balanced

@blarghmatey
blarghmatey merged commit 60dcc2f into main Nov 2, 2026
23 checks passed
@blarghmatey
blarghmatey deleted the version-witan-council-0.46.0 branch November 2, 2026 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants