deepseek-harness/native/landlock-run/pnpm-workspace.yaml at 194ea6bdf0d8a9cdec2e94de9f1f992b44f6f7d0 - deepseek-harness - Gitea: Git with a cup of tea

kevin/deepseek-harness

0 Fork 0

Files

T

kingwl 0a486f09c9 chore: adopt node-addon-landlock-run source as native/ subtree

Bring the node-addon-landlock-run tree (tag v0.0.1, commit 614f7fd) into
native/landlock-run as its source of record: launcher development happens
here, next to the harness consumers, and the standalone repository becomes
the release mirror the tree is exported to for packing and publishing
(procedure in native/README.md). The subtree keeps its own pnpm workspace
and lockfile and is NOT added to the harness workspace: harness installs,
gates, and CI never touch it. The mirror's .github/ stays out of the
subtree; a separate manually-dispatched workflow
(.github/workflows/landlock-run.yml) runs the subtree's CI legs — the
per-architecture native builds, real-kernel launcher proofs, and pack
rehearsal — adapted with working-directory/cache paths.

eslint ignores the subtree like vendor/; AGENTS.md gains the native/
layout line (+5 words on its budget ceiling).

2026-07-14 23:39:58 +08:00

9 lines

246 B

YAML

Raw Blame History

 packages:
   - packages/*
 # pnpm 10+ blocks any dependency shipping an install/build script until it is
 # explicitly reviewed here. Deny by default; esbuild (tsx's bundled native
 # binary) genuinely needs its script.
 allowBuilds:
   esbuild: true