devlake-dev-planning

name	devlake-dev-planning
description	gh-devlake roadmap, milestones, versioning, and release priorities. Use when asking about what's planned, what version something targets, or what issues exist for a milestone.

gh-devlake Roadmap Lookup

Repository

• Owner: DevExpGBB
• Repo: gh-devlake
• Project Board: https://github.com/orgs/DevExpGbb/projects/21 (Project #21)
• Milestones URL: https://github.com/DevExpGBB/gh-devlake/milestones

How to Look Up Roadmap Information

Use the GitHub MCP tools to query issues and milestones from DevExpGBB/gh-devlake.

List milestones and their issues

Use mcp_github_list_issues with the repo DevExpGBB/gh-devlake to get issues. Filter by milestone name to see what's in each release.

To find all milestones, use the gh CLI:

gh api repos/DevExpGBB/gh-devlake/milestones --jq '.[] | "\(.title): \(.description) (\(.open_issues) open, \(.closed_issues) closed)"'

To find issues for a specific milestone:

gh issue list --repo DevExpGBB/gh-devlake --milestone "v0.3.4" --json number,title,state,labels

Issue labels

Label	Meaning
enhancement	New feature or request
bug	Something isn't working
refactor	Code restructure, no behavior change
documentation	Docs, skills, instructions

Versioning Scheme

Semantic versioning: MAJOR.MINOR.PATCH

• PATCH bumps for bug fixes, internal refactors, docs, and housekeeping.
• MINOR bumps for any new user-facing feature: new commands, new flags, new plugins — any additive capability.
• MAJOR (1.0) — Reserved for production-ready stability declaration.

Roadmap note: the current post-0.4.0 continuation plan is being tracked as a patch train (0.4.1, 0.4.2, …) even where some releases include additive work. Treat the milestone map below as the source of truth for current release targeting.

Milestone Plan

• 0.3.x — Current development line. CRUD subcommands, restructuring, and lifecycle commands.
• 0.4.0 — Initial multi-tool expansion + plugin UX release. GitLab (#13), Azure DevOps (#14), dynamic flag validation (#59).
• 0.4.1 — gh devlake query foundation (#62) + deterministic deploy recovery (#142).
• 0.4.2 — Copilot SDK insights (#63) + Slack plugin support (#95).
• 0.4.3 — gh devlake diagnose (#64) + installable agent skill (#61).
• 0.4.4 — Preview agentic self-healing workflow (#143).
• 0.4.5 — Amazon Q Developer plugin support (#94) + Poetry workaround cleanup tracking (#79, contingent on upstream fix).
• 0.4.x — Umbrella continuation line only; use the concrete 0.4.x patch milestones above for issue targeting.

Note: Always query GitHub milestones for the latest status — this section is a snapshot.

Current Release Plan

Note: Always query GitHub milestones, current and upcoming releases, and issues for the latest status — this table is a snapshot.

CLI Command Architecture (Option A)

Connection lifecycle commands live under configure connection:

gh devlake configure connection create  --plugin gh-copilot ...
gh devlake configure connection delete  --plugin gh-copilot --id 2
gh devlake configure connection update  --plugin gh-copilot --id 2 --token ghp_new
gh devlake configure connection list
gh devlake configure connection test    --plugin gh-copilot --id 2

Each command operates on one plugin at a time. Interactive mode prompts for plugin selection.

Release Procedure

When creating a new release:

1. Create the release with gh release create <tag> --repo DevExpGBB/gh-devlake --title "<title>" --notes "<notes>" (or --generate-notes when appropriate).
2. Wait for the release workflow — the .github/workflows/release.yml triggers on v* tag push and uses cli/gh-extension-precompile@v2 to build cross-platform binaries. This takes ~60-90 seconds.
3. Verify the workflow finished successfully:

   gh run list --repo DevExpGBB/gh-devlake --workflow release.yml --limit 1
   gh run view <run-id> --repo DevExpGBB/gh-devlake --json status,conclusion,url
   

4. Verify assets were uploaded — this is a separate required gate. Check both the count and the actual names:

   gh release view <tag> --repo DevExpGBB/gh-devlake --json assets --jq '.assets | length'
   gh release view <tag> --repo DevExpGBB/gh-devlake --json assets --jq '.assets[].name'
   

   Expected count: 12 assets:
   • darwin-amd64
   • darwin-arm64
   • freebsd-386
   • freebsd-amd64
   • freebsd-arm64
   • linux-386
   • linux-amd64
   • linux-arm
   • linux-arm64
   • windows-386.exe
   • windows-amd64.exe
   • windows-arm64.exe
5. If the workflow succeeded but assets are missing, keep polling the release first; do not declare success early.
6. If assets never appear or the workflow fails, investigate the run and re-trigger by deleting and re-creating the tag, or manually re-run the workflow.

Never mark a release as complete after only creating the release or only seeing a green workflow. A release is complete only after the workflow succeeds and all 12 expected asset names are present on the GitHub release.

Key Design Decisions

1. One plugin per invocation in flag mode. Interactive mode walks through plugins sequentially.
2. --plugin flag replaces --skip-copilot/--skip-github (positive selection, not negative exclusion).
3. Singular command names (connection, scope, project) — not plurals.
4. Delete/update/test are subcommands, not flags — each is a distinct action with distinct UX.
5. Plugin-specific fields (org, enterprise, repos) are validated per-plugin, not shared across all.