-
-
Notifications
You must be signed in to change notification settings - Fork 89
Retire every deprecation shim #4777
Copy link
Copy link
Closed
Labels
maintainer-onlyOwner-only work — yields no Gittensor points.Owner-only work — yields no Gittensor points.roadmapOn the Wave-2 agent-layer roadmap board (project 9)On the Wave-2 agent-layer roadmap board (project 9)
Description
Metadata
Metadata
Assignees
Labels
maintainer-onlyOwner-only work — yields no Gittensor points.Owner-only work — yields no Gittensor points.roadmapOn the Wave-2 agent-layer roadmap board (project 9)On the Wave-2 agent-layer roadmap board (project 9)
Projects
StatusShow more project fields
Done
Problem: Once the grace/deprecation windows from the npm package rename, the self-host image rename, the config-filename dual-read, the environment-variable dual-read, and the MCP tool aliases have all elapsed, the old names are still live in code and infrastructure.
Area: Cleanup
Proposal: Remove active maintenance of the old npm package names, stop publishing the old container image tag, drop legacy config-filename and environment-variable dual-read support, and remove the MCP tool aliases. Add a single changelog entry documenting the rebrand.
Deliverables:
Acceptance criteria:
Test scenarios:
Resources:
Boundaries:
Part of #4761.