Skip to content

fix(deps): lock the Linux rolldown native bindings so the extension builds in CI - #111

Open
drk-crew[bot] wants to merge 1 commit into
mainfrom
crew/DRK-ROLLDOWN-BINDING
Open

drk-crew[bot] wants to merge 1 commit into
mainfrom
crew/DRK-ROLLDOWN-BINDING

Conversation

@drk-crew

@drk-crew drk-crew Bot commented Oct 5, 2026

Copy link
Copy Markdown

Goal

Goal: fix(deps): lock the Linux rolldown native bindings so the extension builds in CI

Why it matters

npm run build fails in CI on ubuntu (run 37245569802, job build, step npm run build), in the

What changed

package-lock.json | 223 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 223 insertions(+)

Tests

  • crewverify on 9bd37a2df70f in a clean checkout: backend ok, build-shared ok, cli ok, extension base-only failures, install ok, mcp ok
  • inherited base failures (already on main, not caused here): 1
  • verifier verdict: pass

Risk and provenance

  • risk class: R1
  • crew task: DRK-ROLLDOWN-BINDING, tier cheap
  • declared paths: package-lock.json, packages/extension/package.json

AI assistance

  • Written by an AI crew (Kiro CLI workers, Claude verifier); opened by the crew broker. A human reviews and merges.

Windows-generated lock only had @rolldown/binding-win32-x64-msvc and
-wasm32-wasi. npm ci on linux could not install @rolldown/binding-linux-x64-gnu,
causing vite build to fail (npm/cli#4828). Added all 13 missing platform
binding entries (1.2.1, optional: true) via --package-lock-only so CI
installs the correct native binding on each target OS.
@drk-crew drk-crew Bot added the crew label Oct 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant