Repository navigation
version: witan-council 0.46.0 - #578
Merged
Merged
Conversation
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
Contributor
There was a problem hiding this comment.
🟢 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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What are the relevant tickets?
Releases #576 and #577. witan tasks
tk-recall-takes-minutes-on-the-deployed-witan-media-635dbbandtk-witan-memories-are-written-but-rarely-read-nothi-70e74d.Description (What does it do?)
This releases
witan-council0.46.0. Merging it publishes to PyPI, becausepublish-witan.ymlruns when thispyproject.tomlversion line changes. The diff isjust bump witan-council minor: version,uv.lock, and the fragments collected intoCHANGELOG.md.It ships batched
recall, the content budget onrecallandmemory_search, and memories on a firsttask_claim. It also ships three earlier changes that were waiting for a release:ui_urlon tasks and projects (#560),--targetaddressing 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-codeandwitan-corehave fragments pending too, and those are left out because neither package changed for this work.How can this be tested?
just check-versionsreports all 5 packages consistent.publish-witan.ymlsucceeded andwitan-council0.46.0 is on PyPI.duration_mswith{namespace="witan", container="mcp"} |= "mcp.tool_call" | json | tool="recall", and confirmwitan.memory.surfacedlines appear after a first claim.https://claude.ai/code/session_01FGZebE13gZEF6CLzyqkk9s