Roadmap
RepoWrangler's roadmap is organized by confidence, not promised dates:
- Now — active release work.
- Next — ranked work intended to follow the release.
- Later — directional investments whose order may change.
- Shipped — capabilities already available today.
For exact release contents, see the changelog and release notes.
At a glance
| Horizon | Focus | Intended outcome |
|---|---|---|
| Now | Support RepoWrangler v1.1.1 and advance Ranch Hand Public Preview toward GA | A dependable product release, current public demo and documentation, and a primary guided deployment path with explicit Preview boundaries |
| Next | Make setup, access, and operations easier | A new operator can deploy confidently, add users, and understand sync health without editing configuration or querying the database |
| Later | Scale administration, security, providers, and cost visibility | RepoWrangler grows from a strong estate dashboard into a broader operations platform |
Now — support v1.1 GA
Status: GA. RepoWrangler v1.1.1 is the current supported patch release. Ranch Hand v0.1.0-rc.30 is the primary recommended Windows deployment path in Public Preview; manual deployment remains a supported alternative. The immediate focus is operator feedback, deployment safety, and Ranch Hand's GA gates. Support is best-effort and targets the latest patch release only.
Next — ranked post-release work
Work is expected to proceed in this order. The ordering is deliberate; a new item entering this list should displace or move an existing item.
| Priority | Initiative | Outcome | Key dependency |
|---|---|---|---|
| 1 | Ranch Hand GA | Promote the primary guided path from Public Preview to a signed, production-capable lifecycle manager for the latest supported RepoWrangler patch | Signing, production configuration/lifecycle parity, uninstall, upgrades, security/accessibility/real-target UAT, task-tested docs |
| 2 | Invite and manage users | Administrators add or remove allowed identities in the UI without editing environment variables or restarting | Provider identity model |
| 3 | GitLab URL normalization | Pasting a group URL safely resolves to the GitLab origin and produces accurate authentication versus connectivity errors | None |
| 4 | Multi-month cost and billing history | Operators compare at least the current and prior two billing months by organization, repository, product, and SKU | Existing durable daily usage records |
| 5 | Safe in-app update lifecycle | Finish the platform-neutral controller contract, Azure Container Apps adapter, safety/security gates, UI, and lifecycle verification | Immutable release manifests and external deployment approvals |
Ranch Hand Public Preview → GA
Ranch Hand replaces the retired PowerShell/bash bootstrap-script concept. It is a separate Windows-first Go/React lifecycle application, not a RepoWrangler feature screen and not a source-clone script. It consumes the exact release manifest, digest-pinned image, target bundle, SBOM, and provenance published by RepoWrangler.
The public v0.1.0-rc.30 Preview discovers the latest compatible stable RepoWrangler release by default, verifies it, and offers five distinct targets: WSL Compose, Docker Desktop, remote Linux Compose, Cloudflare, and Azure Container Apps. Docker Desktop also has backup-first lifecycle and recovery operations. It is the primary recommended Windows deployment path; clone/fork/manual/custom-CI remains supported.
GA requires approved Authenticode signing and a stable channel; compatibility with the latest supported RepoWrangler patch; guided production credentials, authentication, database, storage, domain, and HTTPS configuration; integrated Azure sign-in; ownership-safe backup/update/restore/rollback/repair and uninstall/data-retention behavior for every GA target; Ranch Hand application and state upgrade compatibility; clean-Windows and real-target UAT; keyboard, screen-reader, zoom, forced-colors, reduced-motion, and high-DPI testing; privileged-adapter, least-privilege, host-key, tamper, downgrade, redaction, dependency, and signed-artifact security gates; and task-tested documentation with a latest-version best-effort support matrix. A target remains Preview until its own production configuration and complete lifecycle tests pass.
Later — directional investments
Security, deployment, and scale
| Initiative | Intended outcome |
|---|---|
| Tier 3 architecture | Compose the existing platform-neutral foundations into a hardened enterprise topology with private networking, HA data, observability, SSO, and RBAC |
| Deployment automation and pipelines | Ship opt-in GitHub Actions and Azure DevOps templates that consume the same versioned deployment-plan contract as Ranch Hand |
Ecosystem and observability
| Initiative | Intended outcome |
|---|---|
| Notifications and controlled operations | Teams, Slack, and Discord notifications; acknowledgements, quiet hours, and a separate guarded write path for reruns |
| Azure DevOps provider | Add Azure Repos, Pipelines, and pull requests as the next repository provider |
| Additional repository providers | Add Bitbucket, Gitea, and Forgejo behind the existing provider interfaces |
| MCP server and role-based views | Expose estate data to AI clients and tailor views to signed-in user roles |
| Deployment-platform cost and quota visibility | Tie Cloudflare and Azure spend to deployed applications and repositories; show projected spend and free-tier consumption |
| Cache, notification, and job seams | Formalize ICacheProvider, INotificationProvider, and IBackgroundJobProvider with production adapters |
Important dependencies
- Ranch Hand and future deployment pipelines consume the same versioned, secret-free deployment-plan contract.
- User management establishes the identity model needed by role-based views.
- Cost and budget work must surface provider capability honestly when a token cannot access billing APIs.
- Tier 3 work builds on the platform-neutral adapters that already ship; it does not replace them.
Shipped
Recent product work
- v1.1.1 session policy — administrators choose a fixed authenticated-session duration from five minutes through 365 days or keep access until the browser session closes; explicit sign-out and provider-disable invalidation remain.
- Administration and reconciliation — connection inventory/detail, connection-specific credentials, stable provider identities, lifecycle-preserving rename/move/removal handling, and discovery/billing/usage operation history.
- Cost & Billing — actual usage by organization, repository, product, and SKU; direct and inherited budgets; Copilot subscription/seat visibility; forecasts, coverage, optimization findings, and CSV export with honest capability states.
- Large-estate navigation — repository and workspace search, filter, sort, and pagination controls keep hundreds of repositories and roughly 100 workspaces manageable.
- Estate Scope usability — connection sections collapse cleanly and a prominent action starts another provider connection from Estate Scope or Administration.
- Deployment clarity and clean PostgreSQL boot — ACA inputs and exact Key Vault secret names appear before deployment steps; PostgreSQL startup no longer initializes or mentions SQLite.
- v1.0 GA — immutable v1.0.0 through v1.0.24 tags; public release notes; verified Cloudflare demo and Azure Container Apps/PostgreSQL production deployments; and explicit support, upgrade, and rollback policy.
- Faster enrichment after discovery — five-minute reconciliation ticks and a ten-job scheduler batch clear provider enrichment promptly without exceeding the existing provider request budget.
- Onboarding and estate scoping — connect GitHub or GitLab, store credentials server-side, and select monitored organizations, groups, and repositories.
- Grow the estate — add organizations or groups to an existing connection and review repositories discovered since the last acknowledgement.
- Sign-out and version visibility — end sessions from the UI and see the deployed version in the sidebar, About page, and health/auth APIs.
- GitLab discovery repair — connect, group selection, and manual sync all enqueue GitLab discovery correctly.
- Wrangler Labs release — full project history, documentation, demo, legal ownership, and governance moved under Wrangler Labs.
Platform foundations
| Area | Shipped capability |
|---|---|
| Storage | SQLite/D1 and PostgreSQL through the shared persistence seam |
| Hosting | Cloudflare Worker and Node/Hono server with self-served SPA and Docker packaging |
| Scheduling | Cloudflare Cron, Node timer, and guarded external tick driver |
| Secrets | Environment, mounted files, Azure Key Vault, and composite resolution |
| Authentication | GitHub, GitLab, Microsoft Entra ID, Google, and local development providers behind one registry |
| Deployment | Cloudflare, Docker, GitHub Pages, Azure SWA, Azure Container Apps, Kubernetes manifests, and Helm |
| Documentation | VitePress site with deployment, architecture, API, configuration, operations, security, and developer guides |
Product phases delivered
- Foundation and governance — public project, CI/CodeQL, demo mode, and host-agnostic frontend.
- GitHub estate MVP — discovery, inventory, Command Center, workflow/PR state, and connection health.
- Branch and change intelligence — estate-wide branches, change requests, comparison semantics, and exclusions.
- Governance, security, budgets, and usage — hygiene checks, security-alert reconciliation, budget sync, estate views, and JSON export.
- GitLab provider — group/subgroup discovery, pipelines, merge requests, branch comparison, optional webhooks, and unified estate views.
RepoWrangler is platform-neutral (ADR-013): no cloud, host, database, or deployment model is required. Cloudflare is the reference implementation, not a product dependency.
Azure DevOps tracking
The public roadmap summarizes the source-of-truth WranglerLabs backlog. Current parent initiatives are Ranch Hand GA (8010), administration and onboarding (8011), Tier 3 (8012), integrations and extensibility (8013), and in-app updates (7998). Multi-month cost and billing history is tracked by 8009. Public demo and documentation currency is tracked by 8043. Child Features and Stories carry the detailed acceptance criteria; an item is not considered shipped until those criteria have verification evidence.