extension_distribution

Katz 0.243

Azure DevOps builds, tests, packages, and publishes the VS Code extension only for tags matching `ext/v*`.
Tags are created by deployment_flow.
The extension version comes from packages / extension / package. json at the tag; the pipeline must not overwrite it from the tag suffix.
The implementation lives in azure-pipelines.yml.
The pipeline builds language, packages, and the extension only; it does not run the site static build or install Playwright ( site_distribution owns site CI ).
Native core-engine binaries for VSIX come from the Azure `build_native` matrix on this git tag ( vsix_native_not_from_npm, rust_binary_distribution, vsix_export ). GitHub Actions still builds and publishes platform packages on `analytical/v*` for CLI / MCP ( npm_distribution ).
Before tests Azure stages matrix artifacts into workspace packages ( `prepare-native-packages.mjs --binary-dir` ) and checks the host optionalDependency ( `scripts/ensure-host-native.mjs --no-build` ).
VSIX packaging follows vsix_export: one VSIX per native_targets tuple; Marketplace selects the VSIX matching the extension-host target ( extension_host_target ).
Marketplace publish is complemented by Open VSX per openvsx_registry.
Pipeline cache and publish parallelism: extension_pipeline_cache, extension_pipeline_publish.

status

in-progress

todo

first multi-target Marketplace publish not yet run

Interactive page: extension_distribution