Changelog

ADO Pilot's version is set by the version field in the marketplace extension manifest (vss-extension.json). The extension and backend are released together; the version in this file always matches the version installed in your Azure DevOps organization.

Each entry follows the Keep a Changelog shape: Added, Changed, Fixed, and Known issues.

Versioning

Versions are major.minor.patch. Patch releases ship bug fixes and small improvements with no migration steps. Minor releases may introduce new dashboard pages, new configuration knobs, or new auth methods. Major releases — none yet — would coincide with a breaking change to the customer-facing surface and a dedicated migration guide.

[0.1.9] — 2026-05-05

Initial public beta of ADO Pilot.

Added

• AI pull request reviews. Two-pass review pipeline (Pass 1 broad scan, Pass 2 refinement and rescission) with inline comments and a tracking summary comment per PR.
• Batch API routing. Reviews use the Anthropic Batch API (50% discount) with prompt caching and Messages API fallback.
• PR status check. Posts the adopilot/ai-pr-review status check on every reviewed PR; can be wired up as a required branch policy. See Status check reference.
• Authentication. PAT-based authentication for v1. Delegated OAuth and service principal authentication are deferred to the v0.2.0 roadmap.
• Review credit billing. Stripe-backed monthly subscriptions metered in review credits (≈500 diff lines per RC, one-RC minimum). Trial allocation of 20 RCs at signup.
• Plans. Starter, Team, and Business tiers (monthly and annual). Enterprise pricing on request.
• Overage policies. Hard-block (default for Starter and Team) and auto-overage (Team and above), with optional overage cap.
• Configuration inheritance. Org → project → repo merge for file exclusion patterns and scalar override for target branch filters.
• Service hook integration. Branded service hook consumer (adopilot) auto-registers two subscriptions per project at install time, authenticated by a per-tenant webhook JWT (90-day JWT lifetime; rotated automatically when fewer than 30 days remain before expiry).
• Dashboard. Onboarding wizard, billing management, configuration editor, team management, and webhook status pages.

Known issues

• Marketplace update lag. Azure DevOps Marketplace propagates extension updates asynchronously. New extension versions can take up to 24 hours to appear in installed organizations; backend deployments roll out immediately.
• Webhook JWT rotation reminder. The 90-day JWT is rotated automatically when fewer than 30 days remain before expiry. If the rotator cannot reach a tenant during that window — for example, a paused organization — webhooks start failing with 401 after expiry until the JWT is manually re-provisioned from the dashboard.
• Service principal and delegated OAuth auth not yet GA. Listed in the v0.2.0 roadmap; v1 customers must use a PAT.
• Admin API not exposed. All administrative actions are dashboard-only in v1. See Admin API.

Roadmap

The next minor release (target v0.2.0) is scoped to:

• Service principal as the recommended primary auth method, with delegated OAuth as the secondary option.
• Public admin API (see Admin API) for quota adjustments, manual retries, and webhook re-provision.
• Expanded webhook diagnostics surface in the dashboard.

This list is indicative and may shift based on customer feedback during the v0.1.x beta.