vercel-azure-devops-extension

## Bug The doesn't handle the Vercel CLI's non-interactive JSON output format. ### What happens When the CLI runs via (non-interactive), it outputs JSON to stdout instead of just the deployment URL. The extension captures the raw JSON as , which causes: 1. PR comments contain raw JSON instead of a clean URL 2. The value is included in the commands in the JSON, leaking the token in PR comments ### Root cause CLI code (): Extension code (vercel-deployment-task-source/src/index.ts): ``Successfully deployed to ${deployURL}`; // raw JSON in PR comment Suggested fix let deployURL = stdout.trim(); try { const parsed = JSON.parse(deployURL); if (parsed.deployment?.url) { deployURL = parsed.deployment.url; } } catch { // stdout is a plain URL (interactive mode), use as-is } Environment Extension: v3.0.1 Vercel CLI: latest Agent: self-hosted macOS ARM64 Azure DevOps Services

The Vercel CLI outputs JSON to stdout when running in non-interactive mode (CI/CD). The extension previously assumed stdout was always a plain URL, causing raw JSON to appear in PR comments and the token to leak in the commands. This also fixes failing on preview deployments because the raw JSON blob was passed as the deployment identifier. Fixes #56

Summary Tightens how the deployment task captures and forwards CLI output. Only the deployment URL is now extracted from stdout; the rest is discarded so unrelated CLI output does not flow into pipeline output variables, logs, or PR comments. Adds defensive scrubbing of known sensitive token patterns at every output boundary in both tasks. Marks as a secret variable when populated from the task input, so the Azure DevOps log scrubber masks it in pipeline logs. Patch-bumps both tasks and the extension manifest.