From 3b8ded29752d530b71d0e101b577bb10bee823d9 Mon Sep 17 00:00:00 2001 From: Tariq Said Date: Wed, 10 Jun 2026 00:49:35 +0400 Subject: [PATCH] docs: record Linux build validation success --- docs/wpcodespace-build-validation.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/docs/wpcodespace-build-validation.md b/docs/wpcodespace-build-validation.md index 6824e73132ebbf..302f7b16c3e934 100644 --- a/docs/wpcodespace-build-validation.md +++ b/docs/wpcodespace-build-validation.md @@ -51,3 +51,23 @@ The next validation phase should verify: - Do not patch nls.messages.js. - Do not treat the failed local macOS build as a product runtime failure. - Do not proceed to WPCodeSpace Docker image consumption until a Linux/CI build path passes. + +## Linux CI validation success + +The WPCodeSpace OpenVSCode Linux build validation workflow has passed after adding the required native Linux build dependencies. + +Validated in GitHub Actions on Linux: + +- npm ci +- npm run compile-web +- no tracked generated workbench.js or nls.messages patching required + +This establishes Linux CI as the supported validation path for WPCodeSpace OpenVSCode source customization. + +Next validation phase: + +1. Identify the correct OpenVSCode server/image build command. +2. Produce a pinned WPCodeSpace OpenVSCode image from this fork. +3. Run the image locally. +4. Verify the WPCodeSpace Chat copy appears in the running OpenVSCode Chat panel. +5. Only then update the WPCodeSpace repo to consume the pinned image.