Releases: sraj0501/Devtrack_
Release list
v3.1.1
DevTrack v3.1.1
DevTrack v3.1.1 is a packaging-compliance patch for the local MCP bundles introduced in v3.1.0.
Changed
- Every MCPB manifest now declares the public DevTrack privacy policy through
privacy_policies. - Every bundled README now contains the Privacy Policy section required for local-connector
directory review. - Packaging and native smoke tests fail if either privacy declaration is missing.
The executable behavior and six read-only MCP tools are unchanged from v3.1.0. The MCP transport
remains local stdio and reads only the SQLite database selected during installation.
Full changelog: v3.1.0...v3.1.1
v3.1.0
DevTrack v3.1.0
DevTrack v3.1.0 is the first public release with the Phase 9 onboarding path and the local MCP
server. The Go daemon remains the offline source of truth; Python/PostgreSQL powers optional AI and
server-side features.
Highlights
- Six local, read-only MCP tools expose active-ticket, commit, pending-action, voice-profile,
ticket-history, and EOD context from DevTrack's SQLite database. - Five platform-specific MCPB bundles support Windows amd64, macOS Intel and Apple Silicon, and
Linux amd64 and arm64. - First-run setup brings Go-native monitoring and MCP online before the optional managed Python
server and Ollama model finish bootstrapping. devtrack doctorreports capability readiness and background bootstrap progress.- Existing Ollama models can be reused immediately; optional OpenAI or Anthropic credentials are
offered only with explicit consent as a temporary setup fast lane. - The Python server now requires PostgreSQL, applies Alembic migrations before serving, and keeps
client-event synchronization opt-in. - HTTP contracts, native Windows SQLite handling, and Windows/Linux CI coverage were strengthened.
MCP safety and privacy
The MCP transport is local stdio. All six tools are marked read-only, non-destructive, idempotent,
and local/no-open-world. MCPB installation asks the user to select an existing devtrack.db; MCP
tool calls do not post comments, change tickets, send reports, or contact the optional Python
server.
See the privacy policy, the
MCP bundle guide, and the
upgrade instructions.
Upgrade
Existing installations can run:
devtrack upgrade
New installations should follow the platform instructions in the README and then run
devtrack setup. To add DevTrack to an MCP client, run devtrack mcp setup in the target project
and verify with devtrack mcp test.
Full changelog: v3.0.10...v3.1.0
v3.0.10
Contributors
Assets 7
v3.0.9
v3.0.8
v3.0.7
v3.0.6 — Windows CLI parity
What's new in v3.0.6
Windows autostart via Task Scheduler
devtrack autostart-install on Windows now creates a proper Task Scheduler task (ONLOGON / HIGHEST) instead of falling through to the macOS launchd path. autostart-status and autostart-uninstall are fully wired up too.
Full cross-platform CLI parity
All commands behave identically on Windows, macOS, and Linux. Platform differences are handled internally:
force-trigger: SIGUSR2 (Unix) / HTTP endpoint (Windows)reload-config: SIGHUP (Unix) / HTTP endpoint (Windows)stop: SIGTERM (Unix) / TerminateProcess (Windows)upgrade: sudo cp (Unix) / rename-then-copy (Windows)- OS notifications: osascript/notify-send (Unix) / PowerShell balloon (Windows)
Windows binary metadata corrected
The embedded version info (versioninfo.json) was stale at 2.2.14. Updated to 3.0.6 and the .syso resource file regenerated.
Binaries
| Platform | File |
|---|---|
| Windows x86_64 | devtrack_windows_amd64.exe |
| macOS Intel | devtrack_darwin_amd64.tar.gz |
| macOS Apple Silicon | devtrack_darwin_arm64.tar.gz |
| Linux x86_64 | devtrack_linux_amd64.tar.gz |
| Linux ARM64 | devtrack_linux_arm64.tar.gz |
Upgrading
devtrack upgrade