From 1e0b7e3fa738eddfee20c6a0915cbc062c9a8fc3 Mon Sep 17 00:00:00 2001 From: oratis Date: Sat, 8 Aug 2026 22:06:52 +0800 Subject: [PATCH] ci: build the workspace before packaging the VSIX MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit build-vscode stamped core's VERSION into packages/core/src/index.ts and went straight to packaging. The VSIX bundles the app-server, which bundles core, and core's package exports point at dist/ — so esbuild could not resolve @deepcode/core/skills, /tools, or /dist/providers/deepseek.js, and the stamped version would never have reached the bundle either. `pnpm release:check` has always built first, which is why the gate passes locally, and publish-cli already had the step. build-vscode was the one path that skipped it. Co-Authored-By: Claude Opus 5 --- .github/workflows/release.yml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index efbd2dd..5b4c3a1 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -182,6 +182,15 @@ jobs: node -e 'process.exit(require("./package.json").version === process.argv[1] ? 0 : 1)' "${{ needs.validate.outputs.version }}" working-directory: apps/vscode + # The VSIX bundles the app-server, which bundles core — and core's package + # exports point at dist/. Without a workspace build first, esbuild cannot + # resolve @deepcode/core/{skills,tools,dist/providers/deepseek.js} and the + # package step dies. `pnpm release:check` has always built first; this job + # was the one path that did not, and publish-cli already gets it right. + # Also required because the step above stamps core's VERSION into source, + # which only reaches the bundle once compiled. + - run: pnpm build + - name: Package VSIX run: | mkdir -p release-artifacts