Skip to content

v2.1.2

Choose a tag to compare

View all tags
@github-actions github-actions released this 21 Jul 23:36
v2.1.2
330c1f9

DevHub 2.1.2

This maintenance update hardens project identity, SSH platform behavior, process ownership, and MCP exposure, then replaces raw release archives with branded native packages.

Highlights

DevHub MCP Server (devhub-mcp)

A read-only MCP server exposes your DevHub catalog as AI-editor tools. The in-app server listens on 127.0.0.1:47821, requires bearer authentication, and provides 9 tools:

Tool Description
list_projects Catalog of all projects with metadata
project_overview README, layout, git state, recent commit, todos
list_tree Gitignore-aware file tree (depth/hidden controls)
read_file Read line ranges of text files with editor-navigable paths
search_content Full-text search across project files
git_status Live branch, upstream, ahead/behind, changed-file stats
git_diff Unified diffs, optionally filtered by path
git_log Commit history pages
list_todos Per-project DevHub todo items

How to Use

There are two ways to connect DevHub to your editor:

Option A: Standalone (stdio): use the installed MCP executable, or build it with cargo build --release -p devhub-mcp, and add it to Zed's context_servers settings:

{
  "context_servers": {
    "devhub-mcp": {
      "command": "/path/to/devhub-mcp",
      "args": [],
      "env": {}
    }
  }
}

Packaged stdio commands are:

  • Windows: C:\Users\<you>\AppData\Local\Programs\DevHub\devhub-mcp.exe
  • Linux: /path/to/DevHub-2.1.2-x86_64.AppImage with
    "args": ["--mcp-stdio"]
  • macOS: /Applications/DevHub MCP.app/Contents/MacOS/devhub-mcp

Option B: DevHub HTTP (Streamable HTTP): toggle the MCP switch inside the DevHub desktop app, then point your editor to the running server:

{
  "context_servers": {
    "devhub-mcp": {
      "url": "http://127.0.0.1:47821/mcp",
      "headers": {
        "Authorization": "Bearer <token-from-devhub-settings>"
      }
    }
  }
}

DevHub generates a 256-bit HTTP token on first start. Copy or regenerate it from Settings. For tailnet access, run tailscale serve --bg http://127.0.0.1:47821, use the resulting HTTPS URL ending in /mcp, and send the same bearer header. Reverse-proxy Host headers are accepted; direct LAN binding is intentionally disabled. HTTP tool calls use stateless Streamable HTTP JSON responses, avoiding long-lived MCP sessions through the proxy.

Todo List

Lightweight per-project todo tracking accessible via devhub-mcp list_todos and the in-editor todo panel.

Artifacts

  • Windows x64: DevHub-Setup-2.1.2-x64.exe
  • Linux x64: DevHub-2.1.2-x86_64.AppImage
  • macOS Apple Silicon: DevHub-2.1.2-arm64.dmg

Every package contains both executable identities, README.md, RELEASE.md, and LICENSE. Platform integration remains native and small:

  • The Windows installer installs both .exe files, each with the DevHub PE icon, plus Start menu and optional desktop shortcuts for the GUI.
  • The Linux AppImage is the visible branded file and includes both ELF executables, XDG desktop metadata, and .DirIcon. Pass --mcp-stdio to dispatch directly to the companion server.
  • The macOS disk image contains DevHub.app and DevHub MCP.app, both with matching ICNS resources. The latter exposes the stdio executable inside its normal app-bundle path.

Raw Linux ELF and macOS Mach-O files do not embed file-manager icon resources. Branding belongs to the AppImage, desktop entry, and .app bundle rather than to an extracted internal command file.

SHA-256 hashes are published in checksums.txt.

Requirements

  • Git for repository workflows.
  • OpenSSH configuration and key-based authentication for SSH projects.
  • A POSIX remote environment with standard command-line tools, or a Windows SSH host with Git for Windows installed.
  • Linux requires a glibc-based system and a Vulkan-capable desktop stack.
  • Release automation supports Authenticode signing on Windows and Developer ID signing plus notarization on macOS when maintainer credentials are configured. Otherwise Windows artifacts are unsigned and macOS bundles use ad hoc signing.

Maintainers configure Windows signing with the WINDOWS_CERTIFICATE_BASE64 and
WINDOWS_CERTIFICATE_PASSWORD repository secrets. macOS uses
MACOS_CERTIFICATE_BASE64, MACOS_CERTIFICATE_PASSWORD, APPLE_ID,
APPLE_TEAM_ID, and APPLE_APP_PASSWORD.

Before running a package, compare its SHA-256 hash with checksums.txt.

Assets 6
Loading