Install/Update test matrix (P1: blocking VSCode 3-OS lane + board) - #1986
Install/Update test matrix (P1: blocking VSCode 3-OS lane + board)#1986dev-punia-altimate wants to merge 13 commits into
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
VSIX Install + Update Matrix — target
|
| Runtime | linux | windows | macos |
|---|---|---|---|
| vscode | ✅ | ✅ | ✅ |
| vscode-insiders | ✅ | — | — |
| code-server | ✅ | — | — |
Update matrix (upgrade baseline → target)
| Runtime / OS | from 0.55.5 | from 0.59.5 | from 0.60.7 | from 0.61.4 |
|---|---|---|---|---|
| vscode (linux) | ✅ | ✅ | ✅ | ✅ |
| vscode (windows) | — | — | — | ✅ |
| vscode (macos) | — | — | — | ✅ |
| code-server (linux) | — | — | — | ✅ |
…-split update matrix, widen release-gate poll + error state, capture CLI stderr
|
✅ CI validated green — the install/update matrix runs and passes end-to-end on real GitHub-hosted runners (run 26679047912). Install matrix (fresh)
Update matrix (upgrade → pr-build)
It already paid for itself: the first run caught a real Windows-only install failure (Node can't Next (separate PRs): P2 = Cursor/Windsurf/Kiro fork lanes (non-blocking, Linux); P3 = the |
✅ Tests — All Passed |
What
Adds a telemetry-weighted install + update test matrix for the extension. Each cell installs the VSIX (fresh or upgrade-from-baseline), launches the editor headless against the hermetic `dbt-core-sample-duckdb` fixture, asserts activation + dbt-project init, and emits a uniform RESULT_JSON. A Python aggregator renders an install matrix and update matrix, posts them to the PR (check + sticky comment) and Slack, and gates the release.
This is P1: the blocking stock VSCode lane on Linux/Windows/macOS (fresh + upgrade), Insiders (non-blocking, Linux), and the existing code-server smoke wrapped into the same board. Forks (Cursor/Windsurf/Kiro) are P2; the `ms-python.python` portability check + Antigravity are P3.
Why (data)
30-day extension telemetry (App Insights): ~48k active installs — macOS 44% / Windows 35% / Linux 21%; VSCode 79% / Cursor 13.5%. Only ~40% on latest; ~19% on pre-0.61. Today the VSIX install/upgrade smoke runs only on code-server/Linux (1.3% of installs) while Cursor (13.5%) and Windows (35%) of the VSIX path are untested. Upgrade baselines (`0.61.4`, `0.60.7`, `0.59.5`, `0.55.5`) come straight from the version distribution.
How it gates
Files
Pending
🤖 Generated with Claude Code