v1.29.0

The browser automation and the MCP server are now plugin packs in repositories of their own, the way d2w security already is. The host keeps the client, the core plugins, the CLI and FHIR, and every pack releases the same version after it.

What moved

Pack	Repository	Documentation	PyPI
d2w browser	dhis2w-browser	site	dhis2w-browser
MCP server, CLI bridge, router	dhis2w-mcp	site	dhis2w-mcp, dhis2w-mcp-bridge, dhis2w-mcp-router

Both repositories carry their history with them. The package names, the d2w browser commands, the dhis2w-mcp / dhis2w-mcp-bridge / dhis2w-mcp-router entry points and every MCP tool name are unchanged, so an install that names the packages picks up the packs as they release 1.29.0.

Installing

• Browser: uv tool install "dhis2w-cli[browser]" as before. The pack registers d2w browser through the dhis2w.plugins.v1 entry point.
• MCP: install dhis2w-mcp (or dhis2w-mcp-bridge, dhis2w-mcp-router) as before. The pack's one mcp plugin registers the tools of every built-in plugin, calling the same core services the CLI does. Its documentation holds the tutorial, the bridge, the router and the tool reference.

In the host

• dhis2w-core no longer depends on fastmcp, and core plugins contribute their CLI only.
• user-group and user-role are no longer plugin names. Their commands were always d2w user group and d2w user role, which are unchanged.
• The pages that moved redirect to the packs' sites.